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

ai-mcp: support publishing MCP list changes to subscribed clients

Aperta
  • Qualcosa non va?
#1,631 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@jherr ci sta già lavorando.

Dal 6/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, api, backend-api-design

Direzione di ricerca

Start from the follow-up to #1627: how createMCPServer registers tools, resources, and prompts and currently advertises listChanged: false while rejecting subscriptions/listen. Design a public publish path for those lists, including multi-instance event sources, auth scoping, Worker-safe keepalives, and cleanup on cancel/disconnect. Done means callers can publish, subscribed clients get the matching MCP notification and a fresh list, listChanged is true only when a publication source exists, plus unit/E2E coverage, API docs, and a changeset.

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

Descrizione

waiting-on: maintainer
Motivation

Follow-up to #1627. createMCPServer currently registers tool, resource, and prompt definitions when it builds a server. It has no public way to publish list-change events. The fix for #1627 advertises listChanged: false and rejects subscriptions/listen, so clients do not open idle streams that hang on Cloudflare Workers.

Applications with changing MCP lists need a supported way to tell connected clients to refresh. A resource template's list callback can return different entries over time, but the server cannot announce that change today.

Proposed capability

Design a public way for callers to publish tool, resource, and prompt list changes. Support MCP subscriptions/listen when a publication source is configured. The design should specify how a changed list is served on subsequent list requests, how events reach clients across server instances, and how a subscription stays healthy while no changes occur.

Acceptance criteria
  • Callers can publish a change for each supported list, and subscribed clients receive the matching MCP notification and can fetch the updated list.
  • The server advertises listChanged: true only for lists it can publish. Without a publication source, it retains the static behavior from #1627.
  • Idle subscriptions send a bounded keepalive or use another Worker-compatible approach; cancellation and disconnect release their resources.
  • The API defines how applications provide a shared event source for deployments with multiple instances and how events stay scoped to the correct caller when authentication is enabled.
  • Unit and E2E coverage exercise publication, client refresh, idle periods, and connection cleanup. Document the API and add a changeset.

Related: #1627.

Lingua principale
TypeScript
Stelle
3.2k
Fork
361
Merge medio
1g 8h
PR unite (30g)
252

Preparare l'ambiente

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 TanStack/ai

Tutte le issue di TanStack/ai

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.