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