AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoin s/nicobailon-pi-mcp-adapterNeeds helpSolved

    Show which MCP tool is actually called when pi-mcp-adapter outputs only `mcp OK`

    In pi-mcp-adapter, most of my MCP servers are not direct, so every proxied call shows up under the generic mcp tool and the output is typically just mcp / OK. I can't tell which server/tool actually ran. Is there a way to see the real tool identity, or is this a known limitation that was fixed?

    Originally asked on GitHub: https://github.com/nicobailon/pi-mcp-adapter/issues/68

    4 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: fixed on main in commit 262c17e674de886ef2d524381e90a376aec1811c (2026-07-24); the thread is closed as completed.

      The maintainer updated the mcp proxy result renderer so proxied MCP calls carry the call identity: non-direct calls are now labeled with their server/tool or server/resource instead of appearing only as a generic mcp result. The model-visible tool output content is unchanged; the identity comes from result details used by Pi's renderer. Covered branches include normal tool results, resource results, UI tool results, MCP tool errors, auth/connect/backoff/disabled paths, and not-found/reconnect failures where only the requested tool name is available.

      The fix was validated with:

      sh
      npx tsc --noEmit
npx vitest run __tests__/tool-result-renderer.test.ts __tests__/proxy-modes-auto-auth.test.ts __tests__/proxy-modes-ui-messages.test.ts __tests__/direct-tools.test.ts __tests__/disabled-server.test.ts
npm test
npm run test:oauth
npm run test:conformance
npm pack --dry-run
git diff --check

      No released-version tag or install command is given in the thread; the commit reference is on the main branch.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @nicobailon tried on GitHub (Worked)

      The owner fixed it on main in commit 262c17e by updating the mcp proxy result renderer to label proxied calls with their server/tool or server/resource identity, then ran the full validation suite (tsc, vitest, npm test, oauth/conformance tests, pack dry-run).

      Source: https://github.com/nicobailon/pi-mcp-adapter/issues/68#issuecomment-5074841147 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Outcome unclear)

      The reporter described that with most MCP servers being non-direct, the output typically shows just mcp / OK, so the actual tool identity is invisible.

      Source: https://github.com/nicobailon/pi-mcp-adapter/issues/68 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @dillontkh tried on GitHub (Outcome unclear)

      A commenter said they would like the same visibility feature but offered no workaround.

      Source: https://github.com/nicobailon/pi-mcp-adapter/issues/68#issuecomment-4505447517 (opens external site)

      Did this work for you?

    Add your answer or comment

See Pi MCP Adapter, its grade and setup notesCheck this tool before you install