/mcp/try · live trace

show me the internals

Different audience than the homepage demo. This page is for the engineering leader who wants the trace, not the answer. portfolioGuideAgent runs against the public https://api.bokendell.com/mcp endpoint — real HTTP round-trip, no localhost bypass. The pre-seeded prompt forces a multi-tool trace so you can see the agent reach for list_projects, get_tech_stack, and per-project lookups in sequence. Full inventory at /reference/tools.

agent: portfolioGuideAgent · runtime: mastra
10 runs / ip / day · jsonrpc 2.0
suggested

"which projects use drizzle, and what's the one place i ended up dropping it?"

Press Run. Each tool call will appear in the trace panel with the real round-trip latency to the public MCP endpoint.

request traceidle
POST https://api.bokendell.com/mcp · jsonrpc 2.0 · no auth
press Run — every tool call below round-trips to the public /mcp endpoint.
point your own client at it
# claude desktop / cursor / cody — drop into config:
{
  "mcpServers": {
    "bo-kendell-portfolio": {
      "url": "https://api.bokendell.com/mcp"
    }
  }
}

# or hit it directly with curl:
curl -X POST https://api.bokendell.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The MCP endpoint stays open whether or not you use this trace. No auth, no rate limit on the MCP itself — the 10/day cap is on the trace UI's LLM calls, not the underlying tools.

⌘Kterminal