Mega MCP Server

MEGA MCP Server

Independent Model Context Protocol server for MEGA Hub. It exposes one stable surface across Cloudflare Worker, local Streamable HTTP, and stdio transports:

• docs searches current official MEGA guidance.
• search resolves live OpenAPI operations.
• execute calls one documented Hub operation within the caller's OAuth scopes.

Domain workflows live in Codex Skills. Large transfers, repository sync, Git, streaming logs, interactive shells, and reproducible automation belong in the mega CLI. MCP and CLI are parallel clients of the same Hub API; neither wraps or depends on the other.

Hosted MCP

The official OAuth endpoint is:

https://mega.tensorplay.cn/mcp

It supports Streamable HTTP, OAuth 2.1 discovery, Dynamic Client Registration, PKCE, and direct bearer tokens for clients that manage their own credentials.

Related public projects

• MEGA Codex plugin: the public Codex marketplace and OpenAI submission materials.
• MEGA Agent Skills: eight standalone Skills installable with the npm-hosted skills CLI.

The MCP server, plugin, and Skills use independent repositories and release versions. The plugin pins a tested snapshot of the standalone Skills.

Authorization model

MEGA Hub remains the policy and data owner. Every execute request forwards the caller's token to Hub, which enforces scopes, resource ownership, organization policy, budgets, and billing.

The protected-resource document advertises these optional scopes:

• repo:read
• repo:write
• repo:delete
• community:write
• jobs:run
• inference:run
• account:keys
• webhooks:manage

The initial OAuth challenge requests only repo:read. MEGA settings and the actual authorization page share server-backed Read, Write, Full, and Custom preferences. Inference remains available but is never enabled by default.

Tool availability is not authorization: all three tools are always visible, and the granted token scopes determine which API operations can succeed.

Legacy tools, bouquet, mix, and spaces URL parameters are rejected. There are no compatibility aliases for the removed domain-specific tools.

Execute safety boundary

execute accepts a structured method, /api/ path, query object, and optional JSON body. It:

• fixes the destination to the configured MEGA Hub origin;
• rejects unsafe paths, embedded query strings, and encoded separators;
• permits only operations present in the live OpenAPI document;
• limits request and response bodies to 1 MB;
• returns status, request ID, location, content type, and parsed response data.

Use the CLI for larger payloads or streaming output.

Deployment modes

No Durable Object is required. Streamable HTTP uses stateless JSON responses and creates one MCP server per request.

Local stdio

Requires Node.js 22 or newer.

DEFAULT_MEGA_TOKEN=mega_xxx \
npx -y @tensorplay/mega-mcp-server

{
  "mcpServers": {
    "mega": {
      "command": "npx",
      "args": ["-y", "@tensorplay/mega-mcp-server"],
      "env": {
        "DEFAULT_MEGA_TOKEN": "${MEGA_TOKEN}"
      }
    }
  }
}

Local HTTP

npm exec --yes --package=@tensorplay/mega-mcp-server -- mega-mcp-server-http

The endpoint is http://127.0.0.1:3000/mcp; health checks use /healthz, and protected-resource metadata is available at /.well-known/oauth-protected-resource/mcp.

codex mcp add mega-local \
  --url http://127.0.0.1:3000/mcp \
  --bearer-token-env-var MEGA_TOKEN

DEFAULT_MEGA_TOKEN is a local-development fallback and must not be configured on a shared server.

Docker

docker build -t mega-mcp-server .
docker run --rm -p 3000:3000 mega-mcp-server

The runtime image is unprivileged and includes a /healthz health check.

OAuth discovery

1. An unauthenticated MCP request returns 401 with resource_metadata and a read-only default scope request.
2. Protected-resource metadata identifies MEGA Hub and every supported scope.
3. Hub publishes OAuth/OIDC discovery metadata.
4. The authorization screen initializes from the saved permission preference and lets the user narrow the current grant before approval.

Direct bearer tokens remain supported for local clients and automation.

Configuration

Only HTTPS Hub overrides are accepted outside localhost development.

Worker deployment

wrangler.jsonc is a provider-neutral public template. For a real deployment, copy it to an untracked environment-specific configuration and supply routes and optional Hub overrides or service bindings there.

npm ci
npm run check
npx wrangler deploy --config /path/to/private-wrangler.jsonc

The optional HUB service binding avoids a public network hop. The optional METRICS binding records method, tool, status, duration, and count only; it never records tokens, arguments, file contents, or results.

Development

npm ci
npm run typecheck
npm test
npm run deploy:dry-run

Security reports follow SECURITY.md. Contribution and release expectations are in CONTRIBUTING.md.

License

MIT