CLI / oroc mcp

oroc mcp

Run a Model Context Protocol (MCP) server for agent tooling.

By default this subcommand speaks JSON-RPC over stdio (stdout is reserved for MCP messages). Use --http to run an HTTP/SSE transport.

Usage#

oroc mcp [options] [<workspace-dir>]

Options#

Option Description
--stdio use stdio transport (default)
--http use HTTP/SSE transport
--host=<host> HTTP bind host (default: 127.0.0.1)
--port=<port> HTTP bind port (default: 0 for ephemeral)
--endpoint=<path> HTTP endpoint path (default: /mcp; normalizes mcp,/mcp,/mcp/)
--token=<token> require this bearer token (default: auto-generated in HTTP mode)
--no-auth disable token auth (loopback only)
--workspace=<path> explicit workspace root (default: current directory or <workspace-dir>)
--config=<path> workspace-relative oro.toml/oro.ini path to use as the active project config
--read-workspace-only restrict filesystem reads to the workspace root (default; compatibility flag)
--allow-read-outside-workspace explicitly allow reading arbitrary files outside the workspace root
--replace-sse-stream allow a new SSE connection to replace an existing one for the same session id
-h, --help show help

Notes#

Stdio mode disables JSON logs and suppresses INFO output so stdout remains valid MCP JSON-RPC.

HTTP mode supports MCP 2026-07-28 requests and MCP 2025-11-25 and 2025-06-18 sessions.

MCP 2026-07-28 clients call server/discover, send per-request metadata and routing headers, and use a long-lived subscriptions/listen POST for notifications; they do not initialize or send a session header. MCP 2025 clients initialize first and then include Mcp-Session-Id on subsequent requests. HTTP bearer authentication is enabled by default.

The server publishes descriptive MCP tool metadata, including standard titles, safety annotations, extension data under _meta, and structured tool results to help human and AI clients choose the right operation without shell parsing.

Use the MCP search_docs tool for topic-driven discovery across README, source-build environment, MCP, API, config, and manpage resources before falling back to manual resource walking.

When --config is omitted, the active config defaults to oro.toml and falls back to oro.ini when that is the only standard project config present in the workspace. resources/list includes the workspace root and, when present, the active config file, project-local docs under conventional paths, and installed runtime-doc:/ references for shipped API, CLI, config, MCP, README, BUILD_ENVIRONMENT.md, llms.txt, and man1/man3/man7 docs when available.

Use runtime-doc:/BUILD_ENVIRONMENT.md for the independent, presence-based NO_ANDROID and NO_IOS source-bootstrap controls; neither variable selects an application build target.

Prefer runtime-doc:/ resources for runtime behavior and API contracts, and workspace:/ resources for the current app's config and local docs.

Examples#

oroc mcp --stdio .

start an MCP server over stdio for the current workspace

oroc mcp --http --host=127.0.0.1 --port=8080 .

expose the MCP server over local HTTP/SSE

Source repository · Edit this page · View Markdown

Quick links

Type to search across the site. Use the up and down arrow keys to choose a result, Enter to open it, and Escape to close.