Extend
Reach Mogplex capabilities from outside Mogplex — local agents (Claude Code, Cursor, opencode, Claude Agent SDK) driving a user's workspace, skills, memories, and agents through the CLI today or the Mogplex MCP server when it ships.
Mogplex is usable from two surfaces that ship today: the web app and the CLI. This section covers the third direction: letting other agents reach Mogplex.
The core question is: your teammate is in Claude Code, Cursor, or a custom Claude Agent SDK app, and wants to use their Mogplex skills, memories, or agents from there — without pasting tokens into a JSON config. What should they do?
Skills (available today)
Anthropic Agent Skills that teach any skill-aware host how to drive a Mogplex workspace through the `mogplex` CLI. Ships today; the MCP-ready substitute.
MCP server (preview)
The Mogplex MCP server — remote Streamable HTTP, OAuth 2.1 + PKCE, no token pasting. Planned; not yet generally available.
Which path is right today
| If the user's agent host… | Use |
|---|---|
| Is skill-aware (Claude Code, Agent SDK, Cursor project rules) | Skills |
| Supports remote MCP with OAuth, and the Mogplex MCP server is live | MCP server |
| Needs scripted, headless access to Mogplex | Use the CLI's automation surface (mogplex run, mogplex runs events --follow) or the v1 REST API directly. Both ship today. |
Skills are the recommended path until the MCP server is generally available. They teach a skill-aware agent to guide the user through the Mogplex cockpit (slash commands, login flow, repo-local config) without ever needing the user to paste a token.
How this section relates to the rest of the docs
- Inbound MCP (Mogplex consuming external MCP servers like Zapier, Notion, Supabase) is covered in Connections and MCP. That direction is live today.
- Outbound MCP (Mogplex exposed as an MCP server to external agents) is covered here at MCP server.
- CLI Skills documentation lives under CLI → Skills. The Skills page in this section is a pointer; the canonical reference is under CLI.
Design principles this section follows
- No pasted tokens. Whether the user picks Skills or MCP, the auth flow owns the credential — either the cockpit's in-app login writing to
~/.mogplex/auth.json(Skills path) or OAuth 2.1 + PKCE against the browser session (MCP path). In both cases the external agent never sees raw auth material. - One source of truth per capability. Tools, agents, skills, and memories are implemented once in the Mogplex runtime. Skills point the user at the cockpit; MCP exposes the underlying services directly.
- Auth preflight is mandatory. Both paths require a working credential before any action runs. Skills enforce it with a
command -v mogplexinstall check and a recommendation to launch the cockpit; MCP enforces it at the Streamable HTTP bearer-token middleware.