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