get_door_effect_summary — frc mcp MCP Tool Read-only
get_door_effect_summary
(get door effect summary) is one of 14 tools on the
frc mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_door_effect_summary from your client
- Claude Code frc mcp get_door_effect_summary run in your project directory
- Claude Desktop frc mcp get_door_effect_summary ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor frc mcp get_door_effect_summary ~/.cursor/mcp.json
- VS Code frc mcp get_door_effect_summary .vscode/mcp.json
- Zed frc mcp get_door_effect_summary ~/.config/zed/settings.json
- Windsurf frc mcp get_door_effect_summary ~/.codeium/windsurf/mcp_config.json
- Cline frc mcp get_door_effect_summary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI frc mcp get_door_effect_summary ~/.gemini/settings.json
- Grok frc mcp get_door_effect_summary .mcp.json (in your project root)
- ChatGPT frc mcp get_door_effect_summary Settings → Connectors → Advanced → Developer mode
- Claude.ai frc mcp get_door_effect_summary Settings → Connectors → Add custom connector
- LangChain frc mcp get_door_effect_summary pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http frc-mcp https://frc-mcp.ziyetis.workers.devOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.