trace_transaction — DERO MCP Server MCP Prompt
trace_transaction
is one of 5 prompts on the
DERO MCP Server
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke trace_transaction from your client
- Claude Code DERO MCP Server Prompt/trace_transaction run in your project directory
- Claude Desktop DERO MCP Server Prompt/trace_transaction ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DERO MCP Server Prompt/trace_transaction ~/.cursor/mcp.json
- VS Code DERO MCP Server Prompt/trace_transaction .vscode/mcp.json
- Zed DERO MCP Server Prompt/trace_transaction ~/.config/zed/settings.json
- Windsurf DERO MCP Server Prompt/trace_transaction ~/.codeium/windsurf/mcp_config.json
- Cline DERO MCP Server Prompt/trace_transaction ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DERO MCP Server Prompt/trace_transaction ~/.gemini/settings.json
- Grok DERO MCP Server Prompt/trace_transaction .mcp.json (in your project root)
- ChatGPT DERO MCP Server Prompt/trace_transaction Settings → Connectors → Advanced → Developer mode
- Claude.ai DERO MCP Server Prompt/trace_transaction Settings → Connectors → Add custom connector
- LangChain DERO MCP Server Prompt/trace_transaction pip install langchain-mcp-adapters
Other prompts on this server
DERO MCP Server also offers 4 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.