compatibility — Figma URL Shape MCP Tool
compatibility
(compatibility) is one of 30 tools on the
Figma URL Shape
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compatibility from your client
- Claude Code Figma URL Shape compatibility run in your project directory
- Claude Desktop Figma URL Shape compatibility ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Figma URL Shape compatibility ~/.cursor/mcp.json
- VS Code Figma URL Shape compatibility .vscode/mcp.json
- Zed Figma URL Shape compatibility ~/.config/zed/settings.json
- Windsurf Figma URL Shape compatibility ~/.codeium/windsurf/mcp_config.json
- Cline Figma URL Shape compatibility ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Figma URL Shape compatibility ~/.gemini/settings.json
- Grok Figma URL Shape compatibility .mcp.json (in your project root)
- ChatGPT Figma URL Shape compatibility Settings → Connectors → Advanced → Developer mode
- Claude.ai Figma URL Shape compatibility Settings → Connectors → Add custom connector
- LangChain Figma URL Shape compatibility pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http figma-url-shape https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/figma-url-shape/mcpOther tools on this server
- figma-url-shape
- utc-time
- timezone
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- status-catalog
- iana-zones
- web-fetch
- fetch-status
- github-repo-shape
- weather-hint
- memory-key-count
- file-path-ok
- browser-url-ok
- think-steps
- search-query-len
- hn-front-count
- lib-docs-hint
- playwright-url-ok
- jira-key-shape
- geo-hint
- calc-eval
- wiki-title-ok
- agent-tool-index
- people-search-index
- agent-ads-index
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.