CorvexCorvex Documentation
Integrations

MCP setup

How the app exposes keys, OAuth clients, and a remote MCP server for assistants.

The MCP integration page is built for assistant access, not generic API browsing.

What it exposes

  • API keys,
  • OAuth clients,
  • server settings,
  • and a remote MCP server URL.

Tool groups

  • Read
  • Create
  • Update
  • Upload
  • Delete

That split matters because it lets assistants stay useful without giving them write access everywhere.

  • GET /api/mcp/keys
  • GET /api/mcp/oauth-clients
  • GET /api/mcp/settings
  • GET /api/mcp/server?token=...

What to document

  • how to create or rotate keys,
  • how to register OAuth clients,
  • how Claude Desktop or Claude Code connects to the remote server,
  • and which permissions the assistant does and does not get.

The first version should stay read-focused unless there is a clear admin use case that justifies write actions.

Payment providers

Stripe keys, checkout behavior, and billing-provider setup from the dashboard.

Client portal

Portal settings, branding inheritance, and the fields the app actually persists.

On this page

What it exposesTool groupsRelated routesWhat to document