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