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