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