MadgicxMCP Docs

Claude Desktop

Connect Madgicx MCP to Claude Desktop.

Claude Desktop

Claude Desktop provides native support for MCP connectors, making it easy to connect to Madgicx MCP from your desktop.

Requirements

  • Claude Desktop installed
  • macOS or Windows
  • Anthropic account with Claude access

Setup Instructions

Open Settings

Launch Claude Desktop and click on Settings in the left sidebar, or use the keyboard shortcut:

  • macOS: Cmd + ,
  • Windows: Ctrl + ,

In the Settings menu, click on Connectors in the sidebar.

Add Custom Connector

Click the Add custom connector button.

Enter MCP Server URL

In the dialog that appears, enter the Madgicx MCP server URL:

https://mcp.madgicx.com/mcp

Click Add to continue.

Authorize with Madgicx

A browser window will open for authorization:

  1. Log in to your Madgicx account (if not already logged in)
  2. Select team — Choose which Madgicx team to connect
  3. Review permissions — Review the requested permissions
  4. Authorize — Click the "Authorize" button

After authorization, you'll be redirected back to Claude Desktop.

Enable in Conversations

The Madgicx connector is now available. To use it in a conversation:

  1. Open a new or existing conversation
  2. Click the connectors icon in the input area
  3. Toggle Madgicx to enable it

Tool Permissions

For a smoother experience, you can configure tool permissions so that read-only tools run automatically while write actions still require your approval:

  1. Go to Customize > Connectors > Madgicx
  2. Under Tool permissions, set Read-only tools to Always allow
  3. Keep Write/delete tools set to Needs approval

This way Claude can fetch campaigns, insights, and account data without prompting you each time, while actions like pausing campaigns or changing budgets still require confirmation.

Using the Connector

Once enabled, you can ask Claude to use Madgicx tools. For example:

What Madgicx team am I connected to?

Claude will use the whoiam tool to retrieve your user and team information.

Troubleshooting

Next Steps

On this page