index

A complete reference for the 1MCP command-line interface, including commands, options, syntax, and examples.

In plain words
What is it for?
Use it to learn or verify commands for starting the service, discovering and running tools, configuring agents, managing authentication, and handling runtime connections.
Why use it?
It provides exact lookup information when you know which command you need but do not remember how to use it.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/1mcp-app/agent/index
Clone the repo
git clone --depth 1 https://github.com/1mcp-app/agent
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,336 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.02336
Opus 5 $0.00016 $0.01168
Sonnet 5 $0.00006 $0.00467
Haiku 4.5 $0.00003 $0.00234

Measured 2d ago against content hash 7e54c6cb9439, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

index scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

docs/en/commands/index.md · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Command Reference

This section is the CLI lookup entrypoint. Use it when you already know which command family you need and want exact syntax, options, or examples.

For AI agents, the preferred path is CLI mode: keep MCP behind 1mcp serve, then use instructions, inspect, and run as a progressive-disclosure workflow instead of exposing a broad tool surface directly in the agent loop.

If you are still trying to get a first setup working, use Quick Start before drilling into command details.

Quick Reference

Main Commands

  • serve - Start the 1MCP server (default command)
  • proxy - Start STDIO proxy to connect to running 1MCP HTTP server
  • instructions - Show the CLI playbook and current server inventory
  • inspect - List exposed servers or inspect a tool schema
  • run - Call a tool through a running 1MCP server
  • cli-setup - Install Codex or Claude bootstrap hooks and startup docs
  • auth - Manage authentication profiles for secured servers
  • target - Manage verified Runtime Target Contexts
  • admin - Manage CLI Admin sessions for Runtime Target Contexts
  • app - Manage desktop application MCP configurations
  • mcp - Manage MCP server configurations
  • preset - Manage server presets for dynamic filtering

Global Options

All 1MCP commands support the following global options:

  • --help, -h - Show help information
  • --version - Show version information
  • --config, -c <path> - Specify configuration file path
  • --config-dir, -d <path> - Path to the config directory
  • --cli-session-cache-path <path> - Path template for the run/inspect CLI session cache file; supports {pid} and {scope}

Environment Variables: All global options can be set via environment variables with the ONE_MCP_ prefix:

  • ONE_MCP_CONFIG=/path/to/config.json
  • ONE_MCP_CONFIG_DIR=/path/to/config/dir
  • ONE_MCP_CLI_SESSION_CACHE_PATH=/tmp/1mcp/.cli-session.{pid}

Read the full file on GitHub · 235 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 235 lines · 32 tokens per session scan A 7e54c6cb9439

Subscribe to this mod's changes

index is a command published in the GitHub repository 1mcp-app/agent (494 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,336 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.