Developers who build integrations for Claude can now see exactly how those integrations perform. On June 8, Anthropic launched a connector observability dashboard in public beta, giving admins and owners on Team and Enterprise plans access to a set of metrics covering adoption, health, and usage patterns across Claude's growing connector directory. The launch is paired with a new in-app submission flow for developers who want to add new integrations to the directory without leaving Claude.
What the Dashboard Tracks
The dashboard surfaces four categories of information for each published connector. Adoption data includes active users, total tool calls, and the connector's current ranking within the directory. Health data includes a composite health score alongside raw error rates and average latency per call. Per-tool breakdowns let owners drill into individual tools inside a connector to see which specific operations are producing errors, rather than treating the connector as a single unit. Finally, a product-surface breakdown separates tool call volumes across Claude, Claude Code, Claude Cowork, and other surfaces where connectors run, making it possible to see whether a connector is used primarily in chat, in agentic coding contexts, or across both.
The health score is a composite metric rather than a single raw number. Anthropic has not published the full formula, but the dashboard presents it alongside the underlying error rate and latency data so that owners can understand what is driving it. Per-tool breakdowns are the most operationally useful element for debugging: a connector that passes top-level health checks may still have one tool generating consistent failures, and those failures were previously invisible without querying logs externally.
Connector Observability: Key Details
- Directory size300+ verified third-party connectors
- Dashboard metricsActive users, tool calls, directory rank
- Health trackingComposite score, error rates, latency, per-tool breakdown
- Surface breakdownClaude, Claude Code, Cowork and more
- Access requiredAdmin or Owner on Team or Enterprise plan
- StatusPublic beta as of June 8, 2026
In-App Directory Submission
Alongside the observability tooling, Anthropic added a direct submission flow inside Claude for developers who want to list a new MCP connector in the official directory. The workflow now runs entirely within Claude under Organization settings, accessible by anyone with Admin or Owner access. Previously, developers submitted through an external process. The shift positions the directory as a self-contained platform: build, test, monitor, and submit without leaving the product.
On Enterprise plans, owners can also delegate dashboard access to other users through a custom role that includes Directory management or Libraries permissions, which means engineering and analytics teams can review connector performance without needing full admin privileges. The scope of access controls suggests Anthropic expects connector management to become a routine part of enterprise Claude administration rather than an occasional task.
"There are over 300 third-party connectors in the directory, used by millions of people every day." Anthropic, Claude blog, June 8, 2026
Why This Matters for the MCP Ecosystem
The Model Context Protocol has grown quickly since Anthropic introduced it. The connector directory now includes integrations covering legal research, CRM, financial data, code review, document management, and a long tail of specialized tools. At that scale, the absence of operational visibility was a practical problem. A connector that degrades under load, returns errors on specific input types, or performs differently across Claude and Claude Code was hard for its owner to detect without user complaints or external log analysis.
The observability dashboard is also a signal about how Anthropic wants developers to think about the directory. Marketplaces that treat listing as a one-time event tend to accumulate stale or unreliable integrations over time. Tools for monitoring connector health shift the frame toward ongoing maintenance, which keeps the directory more reliable for end users and gives Anthropic better data on which integrations are actually being used. For enterprise buyers, that reliability matters more than directory size: a smaller set of well-maintained managed connectors is more useful than a large catalog with unpredictable quality.
Connector coverage has expanded recently across several verticals. Anthropic added more than 20 legal MCP connectors earlier this year, and enterprise deployments now routinely stack multiple connectors to give Claude access to internal systems alongside commercial data sources. As those deployments grow more complex, the operational questions become correspondingly harder: which connector is causing the latency spike, and on which surface? The dashboard is Anthropic's answer to a question that enterprise administrators have been asking for some time.
