Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Guidelines for hosts to support Command Line (CLI) MCP Apps

Abierto
#689 0 comentarios 3 reacciones 1 asignado Ver en GitHub

@liady ya está trabajando en esto.

Desde el 17/6/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement

Motivation

  • A MCP app will work out of the box in many browser-based hosts (Claude, ChatGPT, Goose, Cursor), but in very few command-line hosts (Pi MCP Adapter) is the only general purpose one I've seen) . Many dev working primarily in the CLI, so we end up having to write custom integrations for each CLI host.
  • For Datadog's [MCP apps](https://www.datadoghq.com/blog/datadog-mcp-apps/, we had to ship a separate UI host in Claude Code launched via session hook. Due to the nature of the hooks API, communication is one-way, so apis like callServerTool do not work. Codex faces similar challenges.

Proposal

We could provide guidelines for how CLIs (Claude Code, Codex, Goose, Antigravity, etc) could support MCP app so MCP apps written for the desktop/web/mobile hosts can be used by devs without requiring MCPs to be used alongside custom hook/script combos to ship custom host-specific glue code. .

Alternatives

Users adopt CLI tools that offer a plugins API which allows for bidirectional communication and/or native MCP apps integration, like OpenCode and Pi . (Note OpenCode doesn't support it natively https://github.com/anomalyco/opencode/issues/14663 , though the plugin system probably allows for it)

Additional Context

Here's a GIF of an MCP app working with Claude Code CLI using a custom glue program. Ideally we could remove the glue program, and rely on a host that ships with Claude Code itself.

Image
Lenguaje dominante
TypeScript
Estrellas
2.9k
Forks
387
Merge medio
2 h 54 min
PR fusionados (30 d)
7

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/ext-apps

Todos los issues de modelcontextprotocol/ext-apps

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.