Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Connect any AI agent to Elastic Cloud with a single URL

Aperta
  • Qualcosa non va?
#397 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
elasticsearch
Ambito
authentication, backend-api-design, cloud, search

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Nessun dato sulla lingua
Stelle
6
Fork
1
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastic/roadmap

Tutte le issue di elastic/roadmap

Issue simili

Altre issue su Security

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.