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