get_impact_engines — nctr mcp server MCP Tool Read-only
get_impact_engines
(get impact engines) is one of 6 tools on the
nctr mcp server
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_impact_engines from your client
- Claude Code nctr mcp server get_impact_engines run in your project directory
- Claude Desktop nctr mcp server get_impact_engines ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor nctr mcp server get_impact_engines ~/.cursor/mcp.json
- VS Code nctr mcp server get_impact_engines .vscode/mcp.json
- Zed nctr mcp server get_impact_engines ~/.config/zed/settings.json
- Windsurf nctr mcp server get_impact_engines ~/.codeium/windsurf/mcp_config.json
- Cline nctr mcp server get_impact_engines ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI nctr mcp server get_impact_engines ~/.gemini/settings.json
- Grok nctr mcp server get_impact_engines .mcp.json (in your project root)
- ChatGPT nctr mcp server get_impact_engines Settings → Connectors → Advanced → Developer mode
- Claude.ai nctr mcp server get_impact_engines Settings → Connectors → Add custom connector
- LangChain nctr mcp server get_impact_engines pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nctr-mcp-server https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpcOther 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.