MCP setup / Account to client

Connect your MCPs

Generate a scoped key and paste-ready client configuration from one account surface.

Open MCP setup Manage API keys

Before configuration

Prepare the account

Your Monarchic account checks plan access, available MCPs, and credential scope before generating a client file.

01

Confirm MCP access

Sign in, activate a plan, and confirm the MCP is marked available in the product catalog.

  1. ACreate an account or sign in.
  2. BActivate a plan with shared MCP usage.
  3. CSelect the MCPs you want in the generated configuration.
02

Create a scoped key

Open API keys, name the key for its client or environment, and choose the narrowest available scope.

Keep the credential private

Never place a key in source control, screenshots, tickets, or chat. Revoke it immediately after exposure.

03 / Client configuration

Generate, paste, restart

The signed-in workspace provides the package name, API URL, credential variable, and format for your selected client.

Generic configuration shape

Illustrative values only

{
  "mcpServers": {
    "your-mcp": {
      "command": "pnpm",
      "args": ["dlx", "<package-from-dashboard>"],
      "env": {
        "MONARCHIC_API_BASE_URL": "<url-from-dashboard>",
        "MONARCHIC_API_KEY": "<your-api-key>"
      }
    }
  }
}

Use the generated values for your account. The placeholders above are illustrative and will not connect as written.

Client flow

  1. 01

    Choose

    Select your AI client and the MCPs to add.

  2. 02

    Paste

    Use the file or settings location shown with the generated config.

  3. 03

    Restart

    Fully quit and reopen the client so it loads the server.

Supported setup formats

Claude DesktopClaude CodeCodexCursorContinue.devCline (VS Code)WindsurfVS Code CopilotZedGoose

Use Generic / raw JSON for another MCP-aware client.

04 / Connection check

Verify with one read-only task

Confirm the connection before assigning broad work or permitting external changes.

  1. 01

    List tools

    Confirm the expected server and tool names appear.

  2. 02

    Read one item

    Run a small request with an answer you can check.

  3. 03

    Inspect the receipt

    Review the evidence and confirm usage appears in the account.

Credential discipline

Keep access scoped

  • 01Use a separate key for each client or environment.
  • 02Start with read-only tools and review write actions.
  • 03Revoke unused credentials and rotate exposed values.

Failure lookup

Common setup problems

The client shows no tools
Confirm the config is in the location shown by the dashboard, then fully restart the client. Check the JSON, TOML, or YAML for syntax errors.
Authentication is rejected
Create a fresh key, copy the full value, and make sure the base URL and credential variable match the generated config.
A specific MCP is unavailable
Check the product status and your current plan. Planned and in-rollout MCPs cannot be connected until access opens.
The adapter will not start
Confirm pnpm is installed and available to the same desktop application or shell that launches the MCP.

Still blocked

Send the exact client error

Include the client and MCP names. Remove credentials before sharing logs or screenshots.

Email support