MCP server (preview)

The Mogplex MCP server exposes Mogplex tools, agents, skills, and memories to any MCP-aware local agent over remote Streamable HTTP, authenticated via OAuth 2.1 + PKCE. Planned; preview state.

The Mogplex MCP server is in preview design state — not generally available. Use Skills today; this page documents the direction of travel so integrators can plan.

What it is

A remote Model Context Protocol server hosted by Mogplex. Any MCP-aware agent host (Claude Code, Cursor, Claude Desktop, opencode, custom Agent SDK apps) will be able to connect and call Mogplex tools, agents, skills, and memories as MCP primitives — without the user pasting a token into a JSON config.

The final endpoint path is not yet committed. Examples on this page use https://mogplex.com/mcp as a placeholder; the shipping URL (exact host, version prefix) will be announced in release notes and this page will be updated then. Do not wire the placeholder URL into production clients.

What it replaces

The substitute available today is the Skills approach (see Skills). Skills teach an external agent to drive Mogplex through the mogplex CLI. The MCP server path replaces that shim with a direct protocol-native integration once the host supports remote MCP with OAuth.

Claude Code / Cursor ──► mogplex.com/mcp  (Streamable HTTP, bearer token)
                              │
                              ▼
              Mogplex tool/agent/skill/memory handlers
              (same code paths the in-app agent uses)

Auth model

Spec-compliant MCP OAuth 2.1 + PKCE, reusing the user's existing Supabase session:

/.well-known/oauth-protected-resource on the MCP endpoint.
/.well-known/oauth-authorization-server on the app origin.
Dynamic Client Registration at /oauth/register so each client (Claude Code, Cursor, a custom app) provisions its own client_id without the user editing any config.
Short-lived access tokens (1h, audience mcp), rotating refresh tokens (30d), stored hashed in Supabase.
Scopes: tools:read, tools:execute, memories:read, memories:write, agents:run, skills:read, workspaces:read. Default grant is read-only; execute and write require explicit consent at the authorize step.

Users manage active clients from Settings → Connections → Local agents (revoke, inspect last-used, see requested scopes).

Tool surface (planned v1)

Each tool is a thin adapter over an existing Mogplex service, not a new capability:

mogplex_list_workspaces, mogplex_get_workspace
mogplex_list_skills, mogplex_get_skill, mogplex_run_skill
mogplex_list_agents, mogplex_run_agent (streamed progress via MCP notifications)
mogplex_search_memories, mogplex_add_memory, mogplex_edit_memory
mogplex_list_rules, mogplex_get_rule
mogplex_run_tool (generic dispatcher)

Mogplex skills are additionally exposed as MCP prompts, since a skill definition maps naturally to that primitive.

Install (once available)

Remote Streamable HTTP — no shim, no token pasting, the host drives OAuth. The shape of the commands below is accurate; the URL is a placeholder that will be finalized when the server ships:

# Claude Code — replace <URL> with the final endpoint from release notes
claude mcp add --transport http mogplex <URL>

# Cursor
# Settings → MCP → Add server → URL: <URL>

For hosts that don't yet speak remote MCP with OAuth, a stdio shim npx -y @mogplex/mcp will ship alongside. The shim runs the OAuth flow once, stores the token in ~/.mogplex/auth.json (same file the CLI uses), and proxies stdio ↔ HTTP.

How it relates to Connections (inbound MCP)

Do not confuse the two directions:

Direction	Where configured	Who authenticates
Mogplex consumes an MCP server (Zapier, Notion, Supabase)	Connections and MCP	Mogplex to the external service
Mogplex exposed as an MCP server	Settings → Connections → Local agents (when live)	External agent to Mogplex

Both can be in use at the same time. An agent running outside Mogplex can call the Mogplex MCP server, and Mogplex can turn around and call a Notion MCP connection from within the same logical tool call.

Status

Design: approved.
Schema, OAuth endpoints, Streamable HTTP handler, stdio shim: planned, not yet merged.
Current public substitute: Skills and the CLI.

When the server ships, this page will update with the live endpoints, the final scope list, and the Settings UI screenshot. Subscribe to release notes or watch the mogplex-cli repo for the @mogplex/mcp package.