# Extend (/extend)



Mogplex is usable from two surfaces that ship today: the [web app](/web) and the [CLI](/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?

<Cards>
  <Card title="Skills (available today)" href="/extend/skills" description="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." />

  <Card title="MCP server (preview)" href="/extend/mcp-server" description="The Mogplex MCP server — remote Streamable HTTP, OAuth 2.1 + PKCE, no token pasting. Planned; not yet generally available." />
</Cards>

## Which path is right today [#which-path-is-right-today]

| If the user's agent host…                                          | Use                                                                                                                                                           |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Is skill-aware (Claude Code, Agent SDK, Cursor project rules)      | [Skills](/extend/skills)                                                                                                                                      |
| Supports remote MCP with OAuth, and the Mogplex MCP server is live | [MCP server](/extend/mcp-server)                                                                                                                              |
| Needs scripted, headless access to Mogplex                         | Use the [CLI's automation surface](/cli/automation) (`mogplex run`, `mogplex runs events --follow`) or the [v1 REST API](/web/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 [#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](/configure-and-extend/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](/extend/mcp-server).
* **CLI Skills** documentation lives under [CLI → Skills](/cli/skills). The [Skills](/extend/skills) page in this section is a pointer; the canonical reference is under CLI.

## Design principles this section follows [#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 mogplex` install check and a recommendation to launch the cockpit; MCP enforces it at the Streamable HTTP bearer-token middleware.