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