MadgicxMCP Docs

Other Clients

Connect any MCP-compatible client to Madgicx MCP via OAuth or client credentials.

Other MCP Clients

Any MCP-compatible client that supports remote servers can connect to Madgicx MCP. There are two ways to authenticate depending on what your client supports.

Use this if your client has built-in OAuth support. The client handles the authentication flow automatically.

Add a new remote server with the URL

https://mcp.madgicx.com/mcp

Complete the OAuth flow

Your client should open a browser window where you log in to Madgicx, select a team, and authorize access.

Verify the connection

Ask your assistant: "What Madgicx team am I connected to?" — it should call the whoiam tool and return your user and team details.

Option 2: Client ID / Client Secret

Use this if your client does not support OAuth but allows you to pass custom headers or tokens. This is the same approach used by Agentic Frameworks.

Get your credentials

Navigate to Workspace Settings → MCP Integration in your Madgicx dashboard and copy your Client ID and Client Secret.

See the Agentic Frameworks credentials guide for detailed instructions.

Obtain an access token

Exchange your credentials for an access token using the token endpoint:

curl -X POST https://mcp.madgicx.com/oauth/token \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "scope=mcp:read mcp:write"

Configure your client

Add the MCP server URL and pass the access token as a Bearer token in the Authorization header:

  • URL: https://mcp.madgicx.com/mcp
  • Header: Authorization: Bearer YOUR_ACCESS_TOKEN

Verify the connection

Ask your assistant: "What Madgicx team am I connected to?" — it should call the whoiam tool and return your user and team details.

Token refresh

Access tokens expire. For long-running integrations, use the MadgicxConfidentialClientAuth helper to handle automatic token refresh, or implement your own refresh logic.

Troubleshooting

On this page