Anthropic adds an observability dashboard and in-app submission flow for Claude MCP connector owners
Claude's new public-beta dashboard gives MCP connector owners usage metrics, error diagnostics, and latency data — plus a direct submission flow to the connectors directory.
If you have published an MCP connector to the Claude Connectors Directory, you now have a dashboard that tells you how it is actually performing. Anthropic shipped two related features on June 8, 2026: a public-beta observability dashboard for connector owners, and an in-app submission flow so developers can get new connectors into the directory without leaving Claude.
Here is what each one does and what it means for you in practice.
The observability dashboard, explained
The dashboard lives under the Directory tab in your Organisation settings in Claude. It surfaces the metrics that connector owners have had to infer indirectly until now.
At a glance you can see:
- Active users over time
- Total tool calls across all Claude product surfaces
- Directory rank so you know where your connector sits relative to others
- Error rates and latency, both as summary numbers and broken down per individual tool
- A composite health score that rolls the above into a single indicator
The per-tool error breakdown is the most practically useful piece. If one tool in your connector is failing at a higher rate than the others, you can identify it without having to instrument your own logging and cross-reference it with Claude’s behaviour. That kind of granularity has been missing from the developer experience here.
The cross-product usage breakdown is also worth noting. The directory serves Claude, Claude Code, and other surfaces, and tool call volumes can vary significantly between them. Knowing where your users are actually engaging helps you prioritise where to focus testing and improvements.
What does this mean for you?
If you have a connector in the directory, the headline benefit is operational visibility you did not have before. You can now see whether a code change improved or degraded reliability, whether a new Claude surface is driving adoption, and whether your error rate is trending in the right direction. Previously, a connector owner’s main signal was indirect feedback or a drop in engagement that was hard to attribute.
The health score is a useful shorthand for teams who want a quick pulse check. For anyone debugging something specific, the per-tool breakdown is where you will spend most of your time.
One practical note on access: the dashboard requires Admin or Owner access on a Team or Enterprise plan. On Enterprise, Owners can delegate access via a custom role that includes the Directory management or Libraries permission. If you are a developer on a Pro plan building a connector, you will need to work with someone who holds the right account tier and role to access these metrics.
The in-app submission flow
The second piece is more straightforward but genuinely removes friction. Previously, submitting an MCP server to the directory involved navigating to external documentation and working through a separate process. Now the submission portal is built into Claude’s admin settings, under the same Directory tab as the observability dashboard.
The submission process itself includes seven policy acknowledgments covering directory guidelines, first-party API usage, financial transactions, AI media generation, prompt injection, conversation data collection, and public documentation. All seven are required. Once submitted, you can track the status and any reviewer feedback directly from the submissions dashboard in the same interface.
A few technical requirements to be aware of before you submit:
- Your MCP server must use Streamable HTTP transport. SSE was deprecated in the March 2025 MCP spec and is not supported.
- If your connector requires authentication, OAuth is required. Pure client credentials flow (machine-to-machine without user interaction) is not supported for directory connectors.
- The MCP connector is available on the Claude API, Claude Platform on AWS, and Microsoft Foundry. It is not currently available on Amazon Bedrock or Vertex AI.
Why this matters at the platform level
The Claude Connectors Directory currently hosts over 300 third-party connectors used by millions of people daily. At that scale, the absence of developer-facing observability was a notable gap. Most mature API platforms give developers usage metrics and error diagnostics as a baseline expectation. Bringing that to Claude connectors is a catch-up to standard practice, but it is a meaningful one for the developers building on top of it.
The in-app submission flow is a smaller quality-of-life improvement, but it signals that Anthropic is treating the connectors ecosystem as a first-class distribution channel that warrants a coherent developer experience rather than a collection of separate docs and portals.
If you are building on MCP and have not yet published to the directory, the submission flow is now the lowest-friction path to getting in front of Claude’s user base. And if you already have a connector live, the dashboard is available in public beta now. It is worth a look before your next release to establish a baseline.