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