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