AgentPing in your editor

Connect AgentPing to your AI editor and ask about your production agents in plain language: what is failing, why a run went wrong, what an evaluation said. Investigation and the fix happen in one place.

It is a hosted MCP server. There is nothing to install: you paste one URL, approve access in your browser, and you are connected.

Connect

The server URL is:

https://agentping.io/mcp

Add it as a remote / HTTP MCP server in your client. The first time you use it, the client opens a browser to AgentPing; sign in, review the permissions, and approve. No secrets to paste, and you can revoke access any time from Settings, Connected apps.

It works with any MCP-capable client that supports streamable HTTP and OAuth. The popular ones:

  • Claude Code: claude mcp add --transport http agentping https://agentping.io/mcp, then run a tool; it opens the browser to authorize.
  • Claude Desktop: Settings, Connectors, add a custom remote connector with the URL above.
  • Cursor: Settings, MCP, add an HTTP server with the URL above.
  • Windsurf: Cascade, MCP servers, add a server with serverUrl set to the URL above.
  • VS Code (GitHub Copilot agent mode): add it to your MCP config as an http server, or run "MCP: Add Server" and pick HTTP.
  • Cline / Roo Code: add a remote MCP server with the URL above.
  • Zed: add it as a context server in your settings.
  • Goose: add an extension of type "Streaming HTTP" pointing at the URL.

Client UIs change; treat each client's own MCP docs as the source of truth. In every case the flow is the same: add the URL as a remote/HTTP server, then approve in the browser.

What you can ask

Once connected, the assistant has read tools (list_teams, list_agents, search_runs, get_run_events, get_run_evaluation) and, on paid plans, tools to acknowledge incidents, give evaluation feedback, and change your monitoring configuration.

A worked example

You: Why did invoicer fail last night?

The assistant calls list_teams to find your team, then search_runs with agent: invoicer, status: failed, and last night's date range. It finds three failed runs, picks the first, and calls get_run_evaluation and get_run_events on it.

Assistant: invoicer failed three times between 02:00 and 02:40. The evaluation says the goal was not achieved: the agent called the lookup_customer tool, got an empty result, and produced an invoice with a blank customer. The upstream lookup returned 200 with an empty body, so nothing errored; the run "succeeded" technically but the evaluation caught the bad output. Here is the run: https://agentping.io/runs/run_eu_...

That is detection to diagnosis without leaving the editor.

What the assistant can and cannot do

Access is honest and bounded:

  • View your agents, runs, and results (the read permission, on every plan).
  • Acknowledge and resolve incidents, and give evaluation feedback (the ops permission, paid plans).
  • Change your monitoring configuration: rules, channels, budgets, status pages (the manage permission, paid plans, admin role).

A connected editor can never change your billing, invite or remove members, create or revoke API keys, or delete your account or your data. Those stay in the dashboard, on purpose: money through an assistant is a fraud surface, and deleting data needs a human in a browser.

Deletions through the assistant require an explicit confirmation that names the exact thing being deleted, so a wrong guess cannot remove the wrong rule. And every change an assistant makes is recorded in your Activity log (account settings) with who, when, via which app, and from what to what.

Disconnect

Revoke the connection from Settings, Connected apps in AgentPing, or remove the server in your client. Revoking takes effect immediately.