Skip to content

Client setup

Devici MCP works with any AI client that speaks the Model Context Protocol over the Streamable HTTP transport. The configuration is the same shape across every client. Drop in the JSON below and you're connected.

The configuration

Add one of the two entries below to your AI client's MCP server config — pick whichever auth form your client supports.

Option 1 — X-Devici-* custom headers (paste-friendly, no encoding):

{
  "mcpServers": {
    "devici-mcp": {
      "url": "https://mcp.devici.com/mcp",
      "headers": {
        "X-Devici-Client-Id": "your client id",
        "X-Devici-Client-Secret": "your client secret"
      }
    }
  }
}

Option 2 — HTTP Basic auth (for clients that only accept a single Authorization header):

{
  "mcpServers": {
    "devici-mcp": {
      "url": "https://mcp.devici.com/mcp",
      "headers": {
        "Authorization": "Basic <base64(clientId:secret)>"
      }
    }
  }
}

Replace <base64(clientId:secret)> with the encoded value — see Authentication → Encoding the Basic auth header for the macOS / Linux / Windows one-liners.

Field Value
url https://mcp.devici.com/mcp
X-Devici-Client-Id The clientId from the API token you created in Devici
X-Devici-Client-Secret The matching secret for that token

Replace your client id and your client secret with the clientId and secret from the API token you created in Devici. See Authentication for how to create one.

Treat the secret like any other API credential

Store it in your secret manager, never commit it to source control, and rotate on a defined cadence.

Verify your connection

Once your client is configured and reloaded, open a chat and ask:

"List my Devici collections."

If you see your collections, you're connected. If you see an error, the troubleshooting section below covers the common ones.

Troubleshooting

Symptom Likely cause Fix
"MCP server unreachable" Wrong URL, or your network blocks mcp.devici.com Verify the URL is https://mcp.devici.com/mcp. Ask your network team to allow the host if egress is restricted.
401 or 403 on every call Credential, scope, or IP-allowlist issue See Authentication → Common errors for the canonical list and fixes.
Empty tool list in the client Session didn't establish, usually the URL or headers were wrong Double-check both, save the config, then reload the client.
Client says "stdio MCP" or "command-based MCP" only Devici MCP is Streamable HTTP only and does not support stdio Switch to a client that supports remote / Streamable HTTP MCP natively.

For the full list of error codes, see Troubleshooting.

See also