MCP ConfigsMay 14, 2026·2 min read

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.

MCP Hub
MCP Hub · Community
Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Mcp
Install
Npm
Trust
Trust: Established
Entrypoint
1mcp serve
Universal CLI install command
npx tokrepo install 5b838f97-06ba-5184-82ab-96e9d58eefb4
install contractmetadata JSONadapter planraw content
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

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

Beelzebub — LLM Deception Runtime (MCP Honeypot)

Beelzebub deploys LLM-powered decoys across SSH/HTTP/TCP/TELNET/MCP; verified 1,989★ and ships Docker Compose, Helm, and a structured CLI.

MCP Configs
MCP Hub

lean-ctx — Context Runtime (MCP + Shell Hook)

lean-ctx is a local-first context runtime (MCP + shell hook) that compresses file reads and CLI output to cut token waste for coding agents.

MCP Configs
MCP Hub

mcp2cli — Turn MCP Servers into CLI Tools, Zero Codegen

Convert any MCP server, OpenAPI spec, or GraphQL endpoint into a full CLI at runtime. Saves 96-99% of tokens wasted on tool schemas every turn.

MCP ConfigsCLI Tools
MCP Hub

mcp-omnisearch — Unified Search MCP Server

Run mcp-omnisearch as an MCP server to unify Tavily, Brave, Kagi, Exa, GitHub search, and extraction tools behind one interface.

MCP Configs
MCP Hub
◈Home🔍Search👤Me