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