Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Connect any AI agent to Elastic Cloud with a single URL

Open
  • Is something wrong?
#397 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
elasticsearch
Domain
authentication, backend-api-design, cloud, search

Research direction

The issue names no repository files, tests, or implementation entry points. Start by decomposing the hosted MCP endpoint, OAuth 2.1 consent and token lifecycle, Serverless project access, and Cloud Console connection management. Done means a globally hosted endpoint supports the listed client, authorization, revocation, and discovery outcomes for Elastic Cloud Serverless.

Written by the indexing model from the issue text.

Description

Component: Elastic Cloud Serverless product-area:platform

What the feature is

mcp.elastic.co is Elastic's entry into AI clients and marketplaces. It's a single hosted MCP endpoint where any AI client can discover and invoke Elastic capabilities, authenticated once across all your Serverless projects.

Many developer platforms already offer hosted MCP endpoints, giving them a presence in AI clients and letting agents connect without shell access or per-deployment configuration. mcp.elastic.co gives Elastic the same: one URL, one OAuth consent, access to your Elastic Cloud Serverless stack from any MCP-compatible AI client.

Value proposition

Today, connecting an AI agent to Elastic requires per-deployment API key management and per-project configuration. There's no org-level entry point, no way to discover your projects from an AI client, and no standard way to authorize access without sharing a static, long-lived key. mcp.elastic.co changes that: one OAuth 2.1 consent flow covers all your Serverless projects and regions, with short-lived tokens and instant revocation.

Elastic's data and search capabilities are now reachable wherever AI agents operate, without shell access or a custom integration per project.

Expected outcome

  • mcp.elastic.co is live as a globally hosted MCP endpoint for Elastic Cloud Serverless
  • Users authenticate once via OAuth 2.1. Short-lived tokens replace static API keys, through a browser-based consent screen.
  • AI clients can search documents, run ES|QL queries, query logs and metrics, manage Serverless projects, and more
  • Works with any MCP-compatible AI client
  • Elastic is discoverable in major AI client marketplaces
  • Organization administrators can view and revoke all agent connections across the org, for security audits and employee offboarding
  • Initially targets Elastic Cloud Serverless. ECH support is planned as a follow-on.

Key user stories / use cases

  • Developer connecting an agent: A data engineer adds mcp.elastic.co to their AI client of choice, authorizes once through a browser consent screen, and the agent can search their Serverless Elasticsearch index, run ES|QL queries, and inspect their Kibana dashboards. No API key created, no per-project configuration required.
  • User managing connections: A user navigates to Connected Applications in the Cloud Console, reviews the agents they've authorized, and revokes access to one they no longer use. The agent's tokens are immediately invalidated across all their projects.
  • Marketplace discovery: A developer browsing an AI client's marketplace finds Elastic listed alongside other developer tools. They add mcp.elastic.co with one click. Elastic's full data and search capabilities are available in their workflow, no configuration needed.
Dominant language
No language data
Stars
6
Forks
1
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/roadmap

All issues in elastic/roadmap

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.