Ask Claude about your AI agents
SuperOrgs now speaks MCP. Paste one URL into Claude, ChatGPT, or Cursor and ask what your agents did today.
Your company runs AI agents. Somebody deployed them, they do work all day, and when someone asks "what did they actually do this week" the answer lives in five dashboards.
Now you can just ask.
SuperOrgs has an MCP server. You paste one URL into Claude, sign in with your SuperOrgs account, and your AI assistant can see your agent workforce. Not a copy of it. The real thing: every agent, every run, what each one costs, and how it all maps to your org chart.
Connecting takes about a minute
- In Claude, open Settings, then Connectors, then Add custom connector.
- Paste
https://app.superorgs.com/mcp - Sign in and pick your organization.
That is the whole setup. No API keys, no config files. The same works in ChatGPT and Cursor, or any client that speaks MCP.
What you can ask
- What did the onboarding agent do today?
- Which agents cost the most this week?
- Why did last night's run fail?
- Which departments have people but no agents yet?
Behind those questions are 16 tools: live activity feeds, run timelines, per-run cost, agent health, error forensics, org chart, and cost anomalies. There are also two built-in prompts (a weekly workforce review and a cost spike investigation) you can run from the attachment menu.
It sees what you can see, nothing more
Every question runs through the same permission checks as the app itself. Your token is scoped to your organization, and your role decides what comes back. If you can only see your own agents in SuperOrgs, that is all Claude can see too. Cross-organization access is not possible by design: the organization comes from your verified sign-in, never from the request.
Why we built it this way
We did not bolt a chatbot onto a dashboard. We built one capability layer that the app, the MCP server, and soon our in-app assistant Orion all share. When we add a capability, every surface gets it at once. Today it is read-only: your assistant can look, not touch. Actions (assign a task, pause an agent, kick off a run) are next, on the same permission rails.
If you already use SuperOrgs, paste the URL and ask something. If you do not, the docs show how the whole thing fits together.