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