{"slug": "manifest-gateway-now-has-a-cli-and-a-remote-mcp-server", "title": "Manifest gateway now has a CLI and a remote MCP server", "summary": "Manifest released a management CLI called mnfst and a remote Model Context Protocol (MCP) server for its gateway, both of which call the same management API as the dashboard so users can create harnesses, connect providers, set routing, and read the request log from a terminal or an AI client. The MCP server runs over HTTP at https://app.manifest.build/api/v1/mcp and authenticates via OAuth with a short-lived, revocable token, offering read-only or read-and-write consent scopes; the CLI is available in the Manifest repository at github.com/mnfst/manifest.", "body_md": "# Manifest gateway now has a CLI and a remote MCP server\n\nThe Manifest gateway is now drivable two new ways: a management CLI, **`mnfst`**, and a remote **MCP server**. Both call the same management API the dashboard does, so you can create harnesses, connect providers, set routing, and read the request log from your terminal or from an AI client.\n\n## Manage the Manifest gateway from the terminal\n\nLog in once, in the browser:\n\n```\nmnfst login\n```\n\n`mnfst login` opens the dashboard, you approve, and the CLI gets a token. The token never travels through the browser.\n\nFrom there, the whole workspace is a command away:\n\n```\nmnfst agent create --name coding-assistant --platform openclaw --category coding\nmnfst provider connect xai --auth-type api_key --credential-env XAI_API_KEY\nmnfst agent configure coding-assistant --models grok-4.5,grok-4 --provider xai\nmnfst routing test coding-assistant\nmnfst requests get --agent coding-assistant --range 7d\n```\n\nThe command set covers harnesses, provider connections, routing (the default chain, custom tiers, [Autofix](/docs/autofix/), and recording), models and prices, the request ledger, and a `doctor` command that tells a wrong URL apart from a wrong credential in one pass.\n\n`mnfst run` is the one built for coding agents. It injects a harness key into a child process without putting it in `argv` or the transcript:\n\n```\nmnfst run --agent coding-assistant -- python agent.py\n```\n\nThe CLI is part of the Manifest repository today:\n\n```\ngit clone https://github.com/mnfst/manifest\ncd manifest && npm install\nnpm run build --workspace=packages/cli\nnpm link --workspace=packages/cli\n```\n\n## Connect any MCP client\n\nThe Manifest gateway also runs a remote [Model Context Protocol](https://modelcontextprotocol.io) server, so MCP clients can manage the workspace directly. It speaks MCP over HTTP and signs in with OAuth: your client opens a consent screen the first time, you approve, and it keeps a short-lived, revocable token.\n\nPoint any MCP client at:\n\n```\nhttps://app.manifest.build/api/v1/mcp\n```\n\nOn a self-hosted install, use your own origin: `https://your-host/api/v1/mcp`.\n\n### Claude Code\n\n```\nclaude mcp add --transport http manifest https://app.manifest.build/api/v1/mcp\n```\n\n### Codex\n\n```\ncodex mcp add manifest --url https://app.manifest.build/api/v1/mcp\ncodex mcp login manifest\n```\n\n### OpenCode\n\nAdd the server to `opencode.json`:\n\n```\n{\n  \"$schema\": \"https://opencode.ai/config.json\",\n  \"mcp\": {\n    \"manifest\": {\n      \"type\": \"remote\",\n      \"url\": \"https://app.manifest.build/api/v1/mcp\",\n      \"enabled\": true\n    }\n  }\n}\n```\n\nThen authorize it:\n\n```\nopencode mcp auth manifest\n```\n\nAny other MCP client works the same way: add the URL and approve in the browser.\n\nThe consent screen asks for read-only or read-and-write access. A read-only connection can look but not touch, and the write tools are not exposed to it at all. The tools mirror the CLI, including a real `routing test` that sends one request through the harness route to prove it works.\n\nThe full setup, discovery endpoints, and tool list are in the [MCP server docs](https://manifest.build/docs/integrations/mcp/).\n\n## Get started\n\n- Dashboard: [app.manifest.build](https://app.manifest.build)\n- CLI: [packages/cli](https://github.com/mnfst/manifest/tree/main/packages/cli)\n- MCP server docs: [manifest.build/docs/integrations/mcp](https://manifest.build/docs/integrations/mcp/)\n- Source: [github.com/mnfst/manifest](https://github.com/mnfst/manifest)", "url": "https://wpnews.pro/news/manifest-gateway-now-has-a-cli-and-a-remote-mcp-server", "canonical_source": "https://manifest.build/blog/manifest-cli-and-mcp/", "published_at": "2026-09-13 00:00:00+00:00", "updated_at": "2026-09-13 16:45:25.176598+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-tools", "ai-infrastructure"], "entities": ["Manifest", "mnfst", "Model Context Protocol", "Claude Code", "Codex", "OpenCode", "xai", "grok-4.5"], "alternates": {"html": "https://wpnews.pro/news/manifest-gateway-now-has-a-cli-and-a-remote-mcp-server", "markdown": "https://wpnews.pro/news/manifest-gateway-now-has-a-cli-and-a-remote-mcp-server.md", "text": "https://wpnews.pro/news/manifest-gateway-now-has-a-cli-and-a-remote-mcp-server.txt", "jsonld": "https://wpnews.pro/news/manifest-gateway-now-has-a-cli-and-a-remote-mcp-server.jsonld"}}