join_agent_challenge — MON$TER Agent Challenge MCP Tool
join_agent_challenge
(join agent challenge) is one of 4 tools on the
MON$TER Agent Challenge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call join_agent_challenge from your client
- Claude Code MON$TER Agent Challenge join_agent_challenge run in your project directory
- Claude Desktop MON$TER Agent Challenge join_agent_challenge ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MON$TER Agent Challenge join_agent_challenge ~/.cursor/mcp.json
- VS Code MON$TER Agent Challenge join_agent_challenge .vscode/mcp.json
- Zed MON$TER Agent Challenge join_agent_challenge ~/.config/zed/settings.json
- Windsurf MON$TER Agent Challenge join_agent_challenge ~/.codeium/windsurf/mcp_config.json
- Cline MON$TER Agent Challenge join_agent_challenge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MON$TER Agent Challenge join_agent_challenge ~/.gemini/settings.json
- Grok MON$TER Agent Challenge join_agent_challenge .mcp.json (in your project root)
- ChatGPT MON$TER Agent Challenge join_agent_challenge Settings → Connectors → Advanced → Developer mode
- Claude.ai MON$TER Agent Challenge join_agent_challenge Settings → Connectors → Add custom connector
- LangChain MON$TER Agent Challenge join_agent_challenge pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-challenge https://monstermoney.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.