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.
npx agentmods add commands/1mcp-app/agent/proxygit clone --depth 1 https://github.com/1mcp-app/agentWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00023 | $0.01413 |
| Opus 5 | $0.00012 | $0.00707 |
| Sonnet 5 | $0.00005 | $0.00283 |
| Haiku 4.5 | $0.00002 | $0.00141 |
Grade A, and why
proxy 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proxy Command
1mcp proxy is the maximum-compatibility bridge on top of a running 1MCP runtime.
It connects a local stdio transport to a running 1mcp serve HTTP runtime. In practice, this is the preferred fallback after CLI mode because most AI clients already support stdio, while fewer support streamable HTTP, SSE, or CLI mode.
Choose the Right Path
1MCP supports three different paths:
- CLI mode for agent loops: recommended for Codex, Claude, and similar agent sessions.
proxy: recommended when you want the broadest client compatibility while keeping project context.- Direct streamable HTTP MCP attachment: use when the client can connect directly and you do not need project context.
proxy is not the main product experience. CLI mode remains the first choice for agent loops. proxy exists as the best non-CLI path when you want stdio compatibility plus .1mcprc and template-server support.
Synopsis
1mcp proxy [options]
What proxy Does
- discovers a running
1mcp serveinstance - forwards stdio MCP traffic to that runtime over HTTP
- can apply preset, filter, or tags selection before exposing the bridged inventory
The runtime still lives in serve. proxy does not replace it.
Auto-Discovery
proxy can discover a running runtime in these ways:
- user-supplied
--url - PID-file-based discovery
- localhost port scan fallback
If project config is present, proxy can also merge settings from .1mcprc.
Project Configuration with .1mcprc
.1mcprc is useful when you repeatedly bridge the same project or client to the same preset or filtered runtime view.
Example:
{
"preset": "development"
}
Priority order is:
- command-line options
.1mcprc- defaults
Common Options
Connection
--url, -u <url>: Override runtime auto-discovery.--context <name>: Use a named Runtime Target Context, including its saved bearer token when present.--config-dir, -d <path>: Use a specific config directory during discovery.
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.
- yesterday First seen · 182 lines · 23 tokens per session scan A 20f4f5827df2
proxy is a command published in the GitHub repository 1mcp-app/agent (494 stars, last pushed 3d ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,413 once invoked, about $0.0001 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.
Other commands, from other repositories
go
MCP tool management and workflow proxy.
strict-development-rules
These rules apply strictly to all code modifications and additions within the Gemini CLI project.
release-harn
Run the tag-first Harn release workflow.
harn-release
Run the tag-first Harn release workflow.
web-component
Create a new web component following the established project conventions.
send
Send a WhatsApp message using the wu MCP server.