MCP

Connect local agents to Mogplex with OAuth, then operate repos, sandboxes, automations, models, runs, and logs through hosted MCP tools.

Mogplex MCP gives local agents a direct, authenticated control surface for the Mogplex platform. Connect once, approve access in your browser, and use the same hosted tools from Cursor, Codex, Claude Code, or OpenCode.

https://www.mogplex.com/api/v1/mogplex/mcp

Choose your local agent

Connect Mogplex

Every client connects to the same hosted endpoint. OAuth opens in your browser, and no API token needs to be pasted into configuration.

Cursor

Open Cursor, register Mogplex, then complete OAuth in your browser.

{
  "mcpServers": {
    "mogplex": {
      "url": "https://www.mogplex.com/api/v1/mogplex/mcp"
    }
  }
}

Install in Cursor

Codex

Copy both commands. Codex binds OAuth to the exact Mogplex resource.

codex mcp add mogplex \
  --url https://www.mogplex.com/api/v1/mogplex/mcp \
  --oauth-resource https://www.mogplex.com/api/v1/mogplex/mcp
codex mcp login mogplex

Claude Code

Install Mogplex, then authenticate from Claude Code with /mcp.

claude mcp add --transport http --scope user mogplex https://www.mogplex.com/api/v1/mogplex/mcp
# Then start Claude Code, run /mcp, select mogplex, and authenticate.

OpenCode

Copy this entry into opencode.json, then authenticate with OpenCode.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mogplex": {
      "type": "remote",
      "url": "https://www.mogplex.com/api/v1/mogplex/mcp",
      "enabled": true
    }
  }
}

Then run opencode mcp auth mogplex.

What agents can do

Install

Connect Cursor, Codex, Claude Code, or OpenCode and complete OAuth.

Tools

Browse the shipped repo, sandbox, automation, model, run, and log tools.

Automations

Create, validate, publish, trigger, and inspect Flow automations safely.

Security

Understand OAuth 2.1, PKCE, token validation, consent, and PAT fallback.

Troubleshooting

Resolve client setup, authentication, tool discovery, and request errors.

Protocol reference

Inspect the transport, OAuth and PAT headers, JSON-RPC envelope, and protocol errors.

One name, two directions

Mogplex MCP is the local-agent entry point

This section documents clients calling Mogplex. If Mogplex needs to call an external service such as Notion, Supabase, or Sentry, configure an external MCP connection instead.

Surface	Direction	Purpose
Mogplex MCP endpoint	Local agent → Mogplex	Operate Mogplex through hosted tools.
External MCP connections	Mogplex → external service	Give Mogplex agents tools from another provider.
External MCP server catalog API	Local host → Mogplex configuration	Sync the external MCP definitions saved in Mogplex.

Transport and compatibility

The endpoint uses remote Streamable HTTP and MCP protocol version 2025-11-25. It is stateless, advertises its protected OAuth resource, and exposes a live tool catalog through tools/list. Clients that support remote MCP OAuth can discover the authorization flow without a pasted API token.

Read Install for client-specific setup or Tools for the complete capability map.