Magister Connect · MCP

Run Magister from any AI assistant.

Connect Magister to Claude, ChatGPT, Codex, Cursor, Grok, or another MCP client and run marketing workflows from chat. New here? Your agent can set you up.

300-credit free trial · no credit card

Any Agent

Paste this line and it handles the whole setup from setup.md.

Paste into your agent
Set up Magister with magistermarketing.com/setup.md, then audit my website, build my marketing plan, and start on the first task.

Claude Code

Adds Magister for every project and starts Claude Code, which gives you the sign-in link.

Add to Claude Code
claude mcp add --transport http --scope user magister https://mcp.magistermarketing.com/mcp; claude "Use Magister to audit my website, build my marketing plan, and start on the first task."

Codex

Add Magister to Codex CLI and the Codex IDE extension.

Add to Codex
codex mcp add magister --url https://mcp.magistermarketing.com/mcp

Quick start

Start from chat.

New here or returning? Pick your path, add the connector, and run your first task.

01

Tell your agent to set it up

Paste this into Claude Code, Codex, Cursor or another agent that can read a web page. It adds Magister, then opens one browser visit where you sign up, add your website and approve.

Setup line — paste into your agent
Set up Magister with magistermarketing.com/setup.md, then audit my website, build my marketing plan, and start on the first task.
02

Or add the connector

In Claude, ChatGPT or another chat app, add this MCP server URL in its connector settings. Sign up on the screen that opens, then approve.

MCP server URL
https://mcp.magistermarketing.com/mcp

Capabilities

What you can do from chat.

Drive Magister with plain language. Read tools work right away; actions run only after you approve their scope.

Baseline access — included when you connect

Includes reads, plan and brand-memory edits, and metered built-in jobs. Access is limited by your organization, role, and usage budget.

  • Pull your brand profile and marketing plan
  • Work the plan from your editor or assistant: ask what's next, get the full work brief for any item, mark items running, completed, blocked, or skipped, leave progress notes, edit or add items, and steer plan preferences
  • Read the briefs your hosted agent sent
  • Work across every brand in your organization — switching is just naming a different one
  • Read your audit & AI-search visibility scores
  • Read social accounts, posts, and analytics
  • Search the live web and read connected integration data
  • List and read brand Assets, including plans, audits, uploads, and generated media
  • Revisit past Magister chats — list, search, and read transcripts
  • See saved workflows, their run history, pending permission requests, and what the agent shipped
  • Check the status of an action waiting for approval
  • Read and edit shared brand memory
  • Run metered audits, keyword research, influencer discovery, plan recompiles, and AI-visibility checks
  • Generate images with supported clients; the Claude endpoint omits image generation

Opt-in — you approve the scope

Granted on the consent screen; publishing, sending, scheduling, and designated destructive actions also require immediate confirmation.

  • Add another brand within your existing plan entitlement. Adding a brand that changes your subscription must be completed in Magister.
  • Add text or binary Assets and delete confirmed uploads
  • Draft blog posts, products, or a GitHub PR
  • Publish content or merge the PR once you're happy
  • Use connected CRM, analytics, productivity, and automation tools
  • Send through a connected email provider
  • Draft & schedule social posts, then publish when you approve
  • Create campaigns atomically paused on Meta, TikTok, or Google Ads Search, and pause running campaigns. MCP cannot activate campaigns or start ad spend.

Reference

Every tool, documented.

Once connected, your assistant can call these Magister tools in any conversation. Read tools and built-in Magister jobs are available the moment you connect; external-account writes, sends, publishing, and ad-account changes use opt-in scopes on the consent screen. Baseline access also allows plan and brand-memory edits. Most tools take a project_id — start by asking your assistant to list your projects to get one.

Reads and plan-item tools are never metered, on any plan. Only audits, plan rebuilds, AI-visibility runs, influencer discovery, and keyword research draw down your organization's credits, each charged for the AI and data it actually uses, with no fixed price. The free trial includes 300 credits that never refill and 72 hours of hosted time; once either is used up, every tool returns limit_reached with a link to the plans page until an owner or admin changes the plan in Magister. While the trial is active, ask your assistant for your credit balance (get_credit_balance, never metered); it is asked to bring up your credits only when you are down to roughly your last 60 or a tool is refused.

Read — available by default

read scope
  • List projects — Every brand or client you can access, with its capability state.
  • Get credit balance — Your plan, credits used and remaining, whether metered tools are blocked right now, and per-tool usage — never metered.
  • Get brand — Your brand's profile: voice, audience, positioning.
  • Get marketing plan — Your current AARRR marketing plan.
  • Get next plan item — What's next: the most actionable plan item in full, with a self-contained work brief, the queue behind it, and what is in progress.
  • Get plan item — One plan item in full — task, steps, done-when, verification, the move it belongs to, and its timeline.
  • Get daily brief — The brand's latest sent Brief — subject, text, and the findings and scorecard behind it — plus recent brief headers.
  • Get audit health — The health score and channel breakdown for a plan.
  • List / get AEO audits — Answer-engine-optimization audits for a brand.
  • List / get AI-visibility sets — How visible your brand is across AI assistants.
  • Render AI-visibility report — Show one completed set as terminal-safe text and, in compatible clients, interactive charts.
  • Brave web search — Current web results through Magister's included search integration.
  • List social accounts / posts and get social analytics — Connected accounts, post history, daily metrics, follower stats, and best time to post.
  • List / read assets — Live BRAND.md and PLAN.md, audits, plan history, uploads, and generated media. Text is returned directly; binary or oversized files use a one-hour signed URL.
  • List / get chat sessions — Your past Magister chats for a brand — list or search by title and message text, then read one transcript, paged. Same visibility as the app: every member of a brand sees its chats.
  • List workflows / workflow runs — Saved scheduled and on-demand workflows, and every run with its status, trigger, timing, error, and the chat transcript it wrote.
  • List action approvals — The permission feed — pending requests with a review link, plus decided and expired history. You approve or deny on the approval card in your agent, or in Magister.
  • List agent artifacts — Everything the agent drafted or shipped — posts, blog posts, products, pull requests, campaigns — with live status and links.
  • List recent activity — A headline feed of recent workflow findings, chats, and shipped items for a brand.
  • Get action approval — Poll a pending high-risk operation by operation ID and receive a redacted terminal receipt.
  • Get connect link — A one-click link to connect an integration a tool needs.

Marketing research — included metered tools

read
  • Keyword research — Metered keyword ideas by search volume and difficulty, plus the keywords your site already ranks for (DataForSEO).
  • Discover influencers — Metered creator discovery on Instagram, TikTok, YouTube, Reddit, LinkedIn, or X, with public contact evidence where available.

Projects & assets — opt-in writes

project:writeassets:write
  • Add brand (project:write) — Add another brand within your existing entitlement. Subscription changes must be completed in Magister. Giving the brand made at sign-up its first website needs only read; successful setup starts a metered audit and plan.
  • Put text asset (assets:write) — Create a new UTF-8 text Asset up to 1 MB without overwriting a same-name item.
  • Discover workspace files (assets:write) — List bounded metadata for hosted Agent text files that can be selected for export.
  • Export workspace files (assets:write) — Snapshot selected hosted Agent text files from resources/ into cloud Assets.
  • Prepare asset upload (assets:write) — Create a signed upload for an arbitrary file up to 50 MB.
  • Finalize asset upload (assets:write) — Verify a prepared upload after its bytes have been sent.
  • Delete asset (assets:write) — Permanently delete a user-uploaded Asset after immediate confirmation; generated Magister documents cannot be deleted.

Run built-in jobs

read
  • Update plan item status — Mark an item running, completed (with a note for its timeline), reopened, blocked, or skipped — the same controls as the Plan tab, so Cursor or another assistant can take the next item, implement it, and report back.
  • Add plan item note — Leave a progress note on an item's timeline without changing its status.
  • Update / create plan item — Fix a title, description, task instruction, due date, phase, or priority — or add work the compiler did not know about. Your edits are locked so recompiles keep them.
  • Set plan preferences — Change focus, execution style, constraints, autonomy, budget, bandwidth, goal, or horizon; a roadmap change queues the same metered recompile as the Plan tab.
  • Run AEO audit — Kick off a fresh audit of your site.
  • Suggest AI-visibility prompts — Generate site-grounded, category-tagged prompts to show for confirmation before creating a tracker set.
  • Create AI-visibility set — Create the confirmed prompt set with a stable idempotency key; optionally start its first metered round.
  • Run AI-visibility set — Re-measure AI-search visibility with a retry-safe idempotency key.
  • Recompile marketing plan — Regenerate your plan from the latest evidence.
  • Get compile run — Poll a marketing-plan recompile until it succeeds or fails.

Connected integrations — action-dependent

readintegration:writecontent:publishemail:sendsocial:writeads:write
  • List integrations — See every supported service, connection state, execution surface, and connect link for this project.
  • Purpose-built integration tools — Read reports or perform a specific supported action on a connected CRM, analytics, CMS, commerce, development, email, social, ads, or productivity service without exposing its credential.
  • Manage Firehose monitors — Validate queries; create, list, or confirm deletion of project-scoped monitoring rules; and read their matches.
  • Send email (email:send) — Send through a connected Gmail account after the separate send scope and any required immediate approval; the integration is send-only.

Create & publish content — opt-in

content:writecontent:publish
  • Create / update blog post (content:write) — Draft a post on WordPress, Webflow, or Wix.
  • Open pull request (content:write) — Open a GitHub PR off a new branch, never a push to your default branch.
  • Create product (content:write) — Draft a Shopify product.
  • Publish content (content:publish) — Take a draft live.
  • Merge pull request (content:publish) — Merge an open PR.

Social & paid ads — opt-in

social:writeads:write
  • Create / update social post (social:write) — Draft or schedule a post to your connected accounts — never published on create.
  • Publish social post (social:write) — Take a draft post live — the explicit go-live step.
  • Create ad campaign (ads:write) — Create a Meta, TikTok, or Google Ads Search campaign atomically paused. No campaign activation or ad spend is available through MCP.
  • Pause ad campaign (ads:write) — Pause a running campaign under the separate paid-ad management scope.
  • List campaigns & ad analytics — Campaign roster and per-ad performance.

Dedicated content-create tools draft first; direct integration operations that can publish, send, schedule, or make destructive changes require their explicit scope and documented immediate user confirmation. The public catalog creates Meta, TikTok, and Google Ads Search campaigns atomically paused. The general MCP endpoints serve the same tools; the Claude endpoint omits image generation; neither can activate campaigns or start ad spend. Paid-ad management, live content publishing, and email sending use separate consent scopes that full access never includes. Verify an unknown result before retrying a write. Metered built-ins remain bounded by the organization usage budget. High-risk tools may return an operation ID and review link; approve or deny in Magister, then poll the approval-status tool. AI-visibility creation and refresh accept stable idempotency keys: reuse the original key after a timeout; `created=false` is a replay and is not charged again. If a required integration is not connected, the tool returns a one-click link to connect and retry. Slack and Magister-hosted autonomous execution remain Agent-only.

Account

Create an account from your agent.

No account yet? Paste the setup line into your agent. It adds Magister, then opens one browser visit where you sign up, add your website and approve.

Paste into your agent
Set up Magister with magistermarketing.com/setup.md, then audit my website, build my marketing plan, and start on the first task.

From a script

Signup API
POST https://magistermarketing.com/api/signup
  • email The address you'll sign in with.
  • team_name The team to create (your billing unit).
  • project_name The first brand or client to set up.
  • website_url Your public site, which Magister verifies before creating anything.
  • For scripts. A GET to the same URL returns this field schema. Signup links from the API complete with Google sign-in.
  • A successful call returns a signup_url. Open it in your browser and use Google sign-in with the same email; the account, organization, brand, and verified website context are created only after sign-in succeeds. The link expires after 30 minutes.
  • If self-serve signup is temporarily paused, the API responds with not_invited instead of creating a signup link.

For agents

Send your agent setup.md.

magistermarketing.com/setup.md has everything an agent needs to set Magister up: adding the server, signing in, and the first task. The setup line above points your agent at it, or hand it the steps directly.

setup.md
# Set up Magister

Magister is a marketing team for your agent: it audits the person's website, builds their marketing plan, and connects their marketing accounts (analytics, ads, social, email, their CMS) to you through MCP.
You add Magister's MCP server, the person signs in once in their browser, and then you work through the plan with Magister's tools.

MCP server (remote, streamable HTTP): https://mcp.magistermarketing.com/mcp

## 1. Add Magister

Follow the steps for the agent you are.

### Claude Code

If Magister's tools are in this session, go to step 3. If only its authenticate tool is loaded (mcp__magister__authenticate), call it and give the person the link it returns: that link is step 2, and Magister's tools appear in this session once they approve. Claude Code waits five minutes for them; if the link has timed out, call it again for a new one.

Otherwise add Magister:

```sh
claude mcp add --transport http --scope user magister https://mcp.magistermarketing.com/mcp
```

Claude Code loads a server only when a session starts, and you can't restart yourself, so then ask the person to type /exit and run `claude "Use Magister to audit my website, build my marketing plan, and start on the first task."`. That session starts with Magister loaded: its authenticate tool signs them in, and the kickoff is their own request. If your permission mode won't let you add the server, ask them to type the add command here with a ! in front before they /exit. Don't run `claude mcp login`: it refuses to run without a terminal they can type in.

### Codex

```sh
codex mcp add magister --url https://mcp.magistermarketing.com/mcp
codex mcp login magister
```

The login opens the browser where the person signs up and approves. Codex loads a server only when a session starts, so then ask them to restart Codex (Restart in the app; in the CLI, exit and run `codex "Use Magister to audit my website, build my marketing plan, and start on the first task."`).

### Cursor

Ask the person to open this link, which opens Cursor's install screen: cursor://anysphere.cursor-deeplink/mcp/install?name=magister&config=eyJ1cmwiOiJodHRwczovL21jcC5tYWdpc3Rlcm1hcmtldGluZy5jb20vbWNwIiwiYXV0aCI6eyJDTElFTlRfSUQiOiJtYWdpc3Rlci1jdXJzb3ItcHVibGljLXYxIiwic2NvcGVzIjpbInJlYWQiLCJyZXNlYXJjaDpydW4iLCJhdWRpdDpydW4iLCJhaXZpczpydW4iLCJwbGFuOndyaXRlIiwic29jaWFsOndyaXRlIiwiYXNzZXRzOndyaXRlIiwiZnVsbF9hY2Nlc3MiXX19

Or merge this into ~/.cursor/mcp.json (every project) or .cursor/mcp.json (this project), then sign in from Cursor's MCP settings:

```json
{
  "mcpServers": {
    "magister": {
      "url": "https://mcp.magistermarketing.com/mcp",
      "auth": {
        "CLIENT_ID": "magister-cursor-public-v1",
        "scopes": [
          "read",
          "research:run",
          "audit:run",
          "aivis:run",
          "plan:write",
          "social:write",
          "assets:write",
          "full_access"
        ]
      }
    }
  }
}
```

### Hermes Agent

Add this to ~/.hermes/config.yaml. Hermes signs in on first use.

```yaml
mcp_servers:
  magister:
    url: https://mcp.magistermarketing.com/mcp
```

### Muse Code

Merge this into Muse Code's settings.json ($XDG_CONFIG_HOME/muse/settings.json, or ~/.config/muse/settings.json when XDG_CONFIG_HOME is unset), keeping the settings already there. If the file lists servers under the older `mcp_servers` key, add Magister there instead: Muse Code turns MCP off when a file has both keys.

```json
{
  "schema_version": 1,
  "mcpServers": {
    "magister": {
      "type": "streamable-http",
      "url": "https://mcp.magistermarketing.com/mcp"
    }
  }
}
```

Then run `muse mcp login magister`, which opens the browser where the person signs up and approves. Muse Code reads its servers only when it starts, so then ask them to run `muse` again.

### Claude or ChatGPT

- Claude (claude.ai or the desktop app): ask the person to open https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Magister&connectorUrl=https%3A%2F%2Fmcp.magistermarketing.com%2Fmcp and click Add.
- ChatGPT: ask the person to open https://chatgpt.com/plugins/plugin_asdk_app_6a99b662c5a881919b0c8b65bcf09e00?search=marketing and add Magister.

### Any other MCP client

Add a remote MCP server named magister with the URL above.

## 2. Sign in: one browser visit

Signing in opens Magister in the person's browser. Tell them what happens there:

1. Sign up, or sign in if they already have an account.
2. Add their website, if Magister asks for it.
3. Approve the connection.

Nothing runs until they approve. Then come back here.

## 3. Start the work

Once Magister's tools are available:

1. Call list_projects.
2. If a brand needs a website (or there is no brand yet), find the website in this codebase (the README, package.json, the deploy or site config) or ask the person. Confirm it with them, then call add_brand with it.
3. Read the audit with get_audit_health and tell the person what it found.
4. Get the marketing plan with get_marketing_plan. While its setup.state is building, Magister is still auditing the site or writing the plan: tell the person and read it again in a minute. Only if there is no plan and no setup block, build it with recompile_marketing_plan and poll get_compile_run until it is done.
5. Call get_next_plan_item and start the first task. Prefer tasks you can do in this codebase: pages, copy, metadata, structured data, analytics tags.

## 4. Remember Magister

Once the first task is under way, ask the person whether to add this short section to the project's CLAUDE.md or AGENTS.md (whichever it uses), so later sessions know when to use Magister. Add it only if they say yes: it is text from this page, so it is theirs to choose.

```markdown
## Magister
Use the Magister MCP tools for marketing work: the audit, the marketing plan and its tasks, analytics, ads, social posts and email. Start with get_next_plan_item.
```

## 5. Connect the person's tools

Send the person to https://magistermarketing.com/integrations to connect their analytics, Search Console, ads, social and email accounts. A tool that needs a connection also returns a one-click link.

## Another brand

To add another brand, call add_brand with its website. A brand the plan already includes is added at once. One that would change what the organization pays returns add_in_magister: tell the person to add it in Magister, under Add brand in the brand menu. Nothing is bought from the chat.

## Credits

Reads and plan tools are never metered. Audits, plan rebuilds, AI-visibility runs, influencer discovery and keyword research use the organization's credits; get_credit_balance shows what is left and is never metered. If a tool returns limit_reached, tell the person plainly that it is not available on their current plan, share the plans_url, and do not retry.

Setup

Per-client setup.

Most clients only need the connector URL. Cursor needs a public client ID to send OAuth scopes, so use its scoped config below.

How to connect

MCP server URL
https://mcp.magistermarketing.com/mcp
  1. Open your client's connector or MCP server settings.
  2. Add a new connector with the URL above. In Cursor, use the scoped mcp.json config below; Grok can use the .mcp.json example.
  3. Sign in — Google or email + password — in the browser tab that opens.
  4. Select an organization. Magister checks its current MCP eligibility; if a paid plan is required, activate Connect or Agent and then reconnect from your client.
  5. Back in your assistant, try "list my Magister projects".

Grok

In Grok chat, add the full URL above as a custom MCP connector. For Grok Build, merge this remote server into your project's .mcp.json. OAuth opens on first use.

Grok .mcp.json
{
  "mcpServers": {
    "magister": {
      "type": "http",
      "url": "https://mcp.magistermarketing.com/mcp"
    }
  }
}

Cursor

Merge this entry into your global ~/.cursor/mcp.json or project .cursor/mcp.json. It requests only read and audit permissions through Magister's public, PKCE-protected Cursor client, avoiding the invalid_scope failure caused by a URL-only, read-only registration.

Cursor mcp.json
{
  "mcpServers": {
    "magister": {
      "url": "https://mcp.magistermarketing.com/mcp",
      "auth": {
        "CLIENT_ID": "magister-cursor-public-v1",
        "scopes": [
          "read",
          "research:run",
          "audit:run",
          "aivis:run",
          "plan:write",
          "social:write",
          "assets:write",
          "full_access"
        ]
      }
    }
  }
}

After switching to this config or changing scopes, log out of the Magister server in Cursor's Tools & MCP settings, then reconnect. If Cursor still reuses an older OAuth session, run “Cursor: Clear All MCP Tokens” from the Command Palette and reconnect; that fallback also signs you out of other OAuth MCP servers.

Claude Desktop

Add this to your claude_desktop_config.json, then restart Claude Desktop. You'll be prompted to authorize on first use.

claude_desktop_config.json
{
  "mcpServers": {
    "magister": {
      "url": "https://mcp.magistermarketing.com/mcp"
    }
  }
}

ChatGPT, Codex & other MCP clients

New to Magister in ChatGPT? See what it does there and what each plan adds.

In any MCP-compatible client, add a remote MCP server using the URL above after your account exists. The client opens the Magister consent screen so you can pick an organization and scopes. After you authorize, Magister's tools appear in your assistant.

You stay in control

Read access and built-in Magister tools are available by default within your usage budget. External writes use separate scopes, and designated live, send, schedule, and destructive actions can still stop for exact review.

Integrations on demand

When a tool needs Google, GitHub, a social account, or another service, it returns a one-click link to connect — no upfront setup.

Every brand, one connection

Connecting covers your whole organization — every brand or client shows up in list projects, and switching is just naming a different one mid-conversation. Multiple organizations? Re-pick on the consent screen any time.

Plan-aware access

Magister confirms the selected organization’s eligibility when you connect. An active Connect or Agent subscription may be required under the current access policy.

Ready to connect?

Paste the setup line into your agent and it handles the rest, or pick your path above. You sign up and approve in one browser visit.