Elastic Cut 40% of Its MCP Tools to Meet Claude Connector Review Requirements

Summary
Elastic reduced its Elasticsearch MCP catalog from 36 tools to 22 during Anthropic’s Claude connector review. The process prompted annotation and read/write changes, bug fixes, and plans for a centralized MCP server.
Key points
- Anthropic’s review assessed every submitted MCP tool for specification compliance and security, as well as descriptions, response metadata, token efficiency, error messages, and product or license availability.
- The submission checklist required tool annotations and separation of read tools from write tools; Elastic split some combined tools and removed others.
- Annotations such as read-only, destructive, idempotent, and open-world hints help clients set expectations, but the article emphasizes that they are not a security boundary.
- Elastic’s Elasticsearch project catalog went from 36 published tools to 22. The company says the review also identified bugs and led to improvements in tool definitions.
- Per-deployment MCP servers require customer-specific URLs and OAuth configuration. Claude Enterprise supports one directory connector instance; additional instances need custom connectors.
- Elastic says a centralized MCP server and a redesigned tool catalog are planned, with no concrete launch date announced.
Article Details
- Topic
- Elastic’s experience preparing its Agent Builder MCP connector for Claude’s connector directory, including tool annotations, read/write separation, security review, and customer-specific OAuth configuration.
Vendors
Products
ClaudeWhen OAuth 2.1 landed for the Elastic Agent Builder Model Context Protocol (MCP) server, I told my product manager I could get us into Claude's connector directory in "one, two days, tops." It took weeks.Elastic Agent BuilderWhen OAuth 2.1 landed for the Elastic Agent Builder Model Context Protocol (MCP) server, I told my product manager I could get us into Claude's connector directory in "one, two days, tops." It took weeks.Elastic Cloud ServerlessThe Elastic Cloud Serverless connector is now live in Claude’s connector directory. In this blog, we cover what the submission review actually checks, the surprises to plan for, and why we’re evolving our MCPElasticsearchBy the end, our catalog for Elasticsearch projects had shrunk from 36 tools to 22 (a reduction of around 40%) and we’d touched more than 100 tools total.Kibanacustomer-specific configuration form would prompt for a client_id and client_secret pair, retrieved from Kibana. This first published version only displayed:
