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

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

Open
#689 0 comments 3 reactions 1 assignee View on GitHub

@liady is already working on this.

Since Jun 17, 2026.

Assessment

This issue has not been assessed yet.

Description

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
Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
2h 54m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

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 modelcontextprotocol/ext-apps

All issues in modelcontextprotocol/ext-apps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.