Extend
Reach Mogplex from local agents through hosted MCP tools, the headless CLI, the REST API, or portable guidance skills.
Mogplex is available through the web app, CLI, hosted API, and MCP. This section covers portable skills and other extension paths for agents working outside the Mogplex cockpit.
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?
Mogplex MCP
Connect a local agent to Mogplex over remote Streamable HTTP with OAuth 2.1 + PKCE.
Skills
Teach a skill-aware host how to guide users through the Mogplex CLI.
Which path is right
| If the user's agent host… | Use |
|---|---|
| Is skill-aware (Claude Code, Agent SDK, Cursor project rules) | Skills |
| Supports remote MCP with OAuth and should operate Mogplex directly | Mogplex MCP |
| 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. |
Mogplex MCP is the direct programmatic path. Skills remain useful when the host should guide a person through the cockpit rather than call Mogplex tools itself.
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.
- Mogplex MCP (Mogplex exposed to external agents) now has its own top-level MCP section.
- 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.