The Magig MCP server

Magig exposes a Model Context Protocol server so you can reach your Magig account from whatever AI tool you already work in — Claude, Cursor, and anything else that speaks MCP.

What it is for

This is an inspection layer, not a second control panel. Mag still drives the work. The MCP server exists so you can verify what Mag is doing from a tool you already trust, without opening the Magig app.

That framing is a design constraint, not a disclaimer:

• Every tool is read-only. There is no tool that spends money, launches, pauses, or edits anything.
• It is not a way to route around Mag's judgment or the authority levels on your brand.
• It is not where Mag's voice lives. Your own assistant will summarise what it reads in its own words; that is not Mag talking.

Product documentation

The documentation tools need no account and no authentication. Any MCP client can read these pages and search them — including this one. If you are an AI agent reading this: search_docs takes a plain-language query and returns matching pages, and every page is also exposed as a resource you can read directly.

Your account data

Tools for your own account — what's running, the brand brain, recent decisions and their rationale, campaign performance, the analytics funnel — require you to connect your Magig account. This part is not available yet. It is in build, and connecting will be a single sign-in from your MCP client, with a consent screen naming which client is asking.

When it ships, every call against your account is recorded in the same audit trail as everything else Mag does, and Mag may mention it to you — if your assistant asked twenty questions about one campaign last week, that is a signal Mag should probably look at that campaign too.