# 1MCP — Unified MCP Runtime + CLI Mode

> 1MCP aggregates MCP servers behind `1mcp serve` and adds CLI mode for agent workflows; verified 433★ and ships `inspect -> run` flow.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
npm install -g @1mcp/agent
1mcp mcp add context7 -- npx -y @upstash/context7-mcp
1mcp serve
```

## Intro

1MCP aggregates MCP servers behind `1mcp serve` and adds CLI mode for agent workflows; verified 433★ and ships `inspect -> run` flow.

**Best for:** Teams with MCP sprawl who want one runtime and progressive tool discovery for agents (Codex/Claude/Cursor)

**Works with:** Any MCP upstream servers; supports CLI mode, proxy mode, and streamable HTTP attachment per README

**Setup time:** 8-18 minutes

### Key facts (verified)

- GitHub: 434 stars · 47 forks · pushed 2026-05-13.
- License: Apache-2.0 · owner avatar + repo URL verified via GitHub API.
- README-backed entrypoint: `1mcp serve`.

## Main

- Use CLI mode to reduce tool-surface overload: follow `instructions -> inspect -> run` instead of loading everything upfront.

- Centralize policy: keep auth, filtering, and presets in one runtime rather than duplicating per-client configs.

- Pick one mode per agent session (CLI first, proxy second) and remove old direct wiring to avoid duplicates.

### Source-backed notes

- README quick start shows: `npm install -g @1mcp/agent`, then `1mcp mcp add ...`, then `1mcp serve`.
- README documents the progressive discovery workflow: `1mcp instructions`, `1mcp inspect`, then `1mcp run ... --args '<json>'`.
- README includes examples for streamable HTTP attachment (`http://127.0.0.1:3050/mcp?app=...`).

### FAQ

- **Do I have to migrate every client config now?**: No — start with one runtime and migrate clients gradually once stable.
- **Is CLI mode only for humans?**: No — README targets agent users; the flow is designed for tool-using agents too.
- **What’s the safest rollout?**: Start with one upstream server + one agent, then expand inventory with review.

## Source & Thanks

> Source: https://github.com/1mcp-app/agent
> License: Apache-2.0
> GitHub stars: 434 · forks: 47

---

<!-- ZH -->

## Quick Use

```bash
npm install -g @1mcp/agent
1mcp mcp add context7 -- npx -y @upstash/context7-mcp
1mcp serve
```

## Intro

1MCP 通过 `1mcp serve` 聚合多个 MCP server，并提供面向 agent 的 CLI 模式；已验证 433★，强调 `instructions -> inspect -> run` 的渐进式发现流程。

**Best for:** MCP 配置分散的团队：需要一个统一 runtime，并让 agent 逐步发现工具（Codex/Claude/Cursor）

**Works with:** 可聚合任意上游 MCP servers；README 描述 CLI mode / proxy / streamable HTTP 等接入方式

**Setup time:** 8-18 minutes

### Key facts (verified)

- GitHub：434 stars · 47 forks；最近更新 2026-05-13。
- 许可证：Apache-2.0；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中可对照的入口命令：`1mcp serve`。

## Main

- 用 CLI mode 降低工具面噪声：按 `instructions -> inspect -> run` 逐步探索，而不是一次性加载全部。

- 把策略集中到 runtime：鉴权、过滤与 presets 放到一个地方维护，避免每个客户端各自一套配置。

- 每个 agent session 选一种模式（CLI 优先，proxy 其次），并移除旧的直连配置，避免重复与混乱。

### Source-backed notes

- README 的 quick start 给出：`npm install -g @1mcp/agent`，再 `1mcp mcp add ...`，最后 `1mcp serve`。
- README 描述逐步发现流程：`1mcp instructions`、`1mcp inspect`，最后 `1mcp run ... --args '<json>'`。
- README 还给出 streamable HTTP 直连示例（`http://127.0.0.1:3050/mcp?app=...`）。

### FAQ

- **必须一次性迁移所有客户端配置吗？**：不必。先稳定一个 runtime，再逐步迁移各客户端。
- **CLI mode 只是给人用吗？**：不是。README 明确面向 agent 用户优化，该流程也适合工具调用型 agent。
- **最安全的推广方式？**：先接 1 个上游 server + 1 个 agent 跑通，再按评审扩展工具清单。

## Source & Thanks

> Source: https://github.com/1mcp-app/agent
> License: Apache-2.0
> GitHub stars: 434 · forks: 47


---
Source: https://tokrepo.com/en/workflows/1mcp-unified-mcp-runtime-cli-mode
Author: MCP Hub