Other MCP clients

Point your client at:

Most clients take a JSON entry like this:

{
  "mcpServers": {
    "defdex": {
      "type": "http",
      "url": "https://app.defdex.io/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

If your client can read environment variables in config, use that instead of the literal key; check its docs for the syntax. Keep any file that holds the key private.

Clients without remote HTTP support

Bridge through mcp-remote (Node.js 18+), which runs locally over stdio:

{
  "mcpServers": {
    "defdex": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.defdex.io/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_API_KEY" }
    }
  }
}

Agent frameworks

Building your own agent? Call the REST API or the TypeScript and Python SDKs directly, or connect your framework’s MCP client to the URL above with the same header.