Migma MCP Server

For OAuth-capable MCP clients, point the client at https://migma.ai/mcp or discover auth from authorization-server metadata. The client self-registers with Migma using Dynamic Client Registration at POST /oauth2/register, then sends the user through Migma consent; the user only reviews scopes and approves access. No manual client creation in a developer portal is documented; the resulting access_token is a scoped Migma API key.

Create a key in Settings → Developers → API Keys: click Create API Key, choose a name and only the scopes you need, then copy the key immediately because it is shown once. Use it as a bearer token in Authorization, or set MIGMA_API_KEY for tools like the SDK, CLI, or local MCP. Test keys start with sk_test_; production keys start with sk_live_.