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