2.3 · Connect your agent via MCP

MCP is how your AI tools get direct access to your GrowthOS workspaceWorkspaceEverything GrowthOS knows and does for one brand. Every figure, page, and agent in your workspace covers that brand only., the container holding everything GrowthOS knows and does for your brand. Once connected, your agent can pull any page's scores and traffic, read a briefBriefThe plan for one page: the research, structure, and targeting a draft is written from. (the plan for one page) and its research, check your contextContextWhat GrowthOS knows about your company: what you do, the market you sit in, the buyers you write for, and how you sound. Held on 8 screens, and every agent reads context before it does anything. (what GrowthOS knows about your company), and answer portfolio questions, all live from the workspace rather than from whatever you paste into the chat. It's the foundation for publishing via your agent and for the playbook of tasks in the next guides.

The connection is yours personally: you sign in with your own GrowthOS account, and your agent gets read-only access to the workspaces you can already see. Nothing your agent does over MCP can change your workspace.

Where setup lives

In the top bar, open the ⋯ menu and choose MCP under Lab. The MCP Settings page carries the connection URL, per-tool instructions, and a Connected badge once your first request lands. Pick your tool and the steps adjust; here's the short version of each.

Claude (web)

Add the connector

In Claude, open Customize › Connectors › Add custom connector, and paste the connection URL from your MCP Settings page.

On a Claude Team or Enterprise plan, only an Owner can add custom connectors, so have an Owner add it under Organization settings › Connectors first.

Connect and sign in

Select Connect on the GrowthOS connector and sign in with your GrowthOS account. Approve the access prompt and you're done.

Claude Code

Register the server

Run the claude mcp add command shown on your MCP Settings page (it registers the growthx-os server with your connection URL).

Authenticate

In a new session, run /mcp, select growthx-os, choose Authenticate, and sign in with your GrowthOS account.

Cursor

Add the server

Open Settings › Tools & MCPs › New MCP server and paste the mcp.json snippet from your MCP Settings page.

Authorize

Click Connect next to growthx-os and sign in.

Any other MCP-capable tool works the same way: add a server with the connection URL, then sign in with your GrowthOS account when prompted.

Confirm it works

Ask your agent something only your workspace can answer: "Using GrowthOS, what are my top pages by traffic this month?" A real answer means you're connected, and the MCP Settings page shows its Connected badge. The same page lists everything your agent can do, under What your agent can do: finding and auditing pages, traffic and keyword data, briefs and opportunitiesOpportunityA page worth writing or rewriting, proposed by an agent with the reasoning attached. Opportunities wait for your triage: accepting one is what starts production. (proposed pages worth writing or rewriting), and your context documents, all read-only.

Common questions

Does each teammate connect separately? Yes. Credentials are per person, so each teammate signs in with their own account and gets access to the workspaces they already have.

Can my agent change or delete anything through this? No. Every MCP tool is read-only. The one write-shaped act, publishing, happens through your CMS's own integration with the article read from GrowthOS; 5.4 · Polish and publish covers it.

Is this safe to roll out to the whole team? It grants each person's agent the same visibility that person already has, read-only. If someone leaves, removing their GrowthOS seat ends their access, MCP included.