# 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.