Set up the BTT MCPs on your laptop

Who this is for

Every BrisTechTonic team member who uses Claude. AMs, exec, ops -- anyone whose Claude needs to pull live data on clients, run SEO crawls, or search Fathom transcripts.

Time needed

Claude.ai (Chat) users: about 60 seconds. The BTT tools are already installed at organisation level -- you do not need to do anything manually.
Claude Code (terminal) users: about 5 minutes.

If you only use Claude.ai (Chat)

The BTT MCPs are installed at the organisation level on the Claude.ai side. As long as you are signed into claude.ai with your @bristechtonic.co.uk Google account, the BTT tools are already available in every new chat. Try: Look up Acme in the BTT clients.

One exception -- HubSpot. It is a third-party MCP, so the first time Claude calls a HubSpot tool it will open a browser tab asking you to authorise with your HubSpot account. One-time, per AM.

What is an MCP?

Model Context Protocol -- the way Claude talks to other software. Each MCP is a connection between Claude and a system (e.g. our client database, GA4, Search Console, Screaming Frog). BTT has two kinds:

Ops Hub-hosted MCPs -- BTT builds and runs these at ops.bristechtonic.co.uk/api/*-mcp. Token-gated. For Chat users they are wrapped in a single btt-omni-mcp aggregator (one URL, all tools).
Third-party MCPs -- vendor-built (HubSpot, Slack, Gmail, etc.). Each AM authorises on first use.

For Claude Code users -- the fast path

Visit ops.bristechtonic.co.uk/team/mcp-setup and click the CODE tab:

Make sure Claude Code CLI is installed (claude --version should return a version number).
Sign in with your @bristechtonic.co.uk account.
Click Copy all setup commands.
Paste into Mac Terminal and press Enter.
Run claude mcp list to confirm all MCPs show as connected.

Manual setup (if the setup page is unavailable)

Step 1 - Install Claude Code CLI

sudo npm install -g @anthropic-ai/claude-code
claude --version

Requires Node.js v20 or higher. Install Node.js from nodejs.org if needed.

Step 2 - Get your tokens

Open 1Password and find the BTT MCP tokens entry in the BTT shared vault. You will see tokens for: CLIENTS_MCP_TOKEN, GA4_MCP_TOKEN, GSC_MCP_TOKEN, FATHOM_MCP_TOKEN, BTT_PUBLISHER_MCP_TOKEN, DATAFORSEO_MCP_TOKEN, SF_MCP_TOKEN, SEMRUSH_MCP_TOKEN.

Step 3 - Add each MCP

Run each command in Terminal, replacing with the value from 1Password. The URL is always a positional argument -- always wrap it in double quotes.

claude mcp add --transport http btt-clients "https://ops.bristechtonic.co.uk/api/clients-mcp?token=TOKEN"
claude mcp add --transport http btt-ga4 "https://ops.bristechtonic.co.uk/api/ga4-mcp?token=TOKEN"
claude mcp add --transport http btt-gsc "https://ops.bristechtonic.co.uk/api/gsc-mcp?token=TOKEN"
claude mcp add --transport http btt-dataforseo "https://ops.bristechtonic.co.uk/api/dataforseo-mcp?token=TOKEN"
claude mcp add --transport http btt-fathom "https://ops.bristechtonic.co.uk/api/fathom-mcp?token=TOKEN"
claude mcp add --transport http btt-publisher "https://ops.bristechtonic.co.uk/api/btt-publisher-mcp?token=TOKEN"
claude mcp add --transport http btt-sf "https://ops.bristechtonic.co.uk/api/sf-mcp?token=TOKEN"
claude mcp add --transport http btt-semrush "https://ops.bristechtonic.co.uk/api/semrush-mcp?token=TOKEN"
claude mcp add --transport http hubspot "https://mcp.hubspot.com/anthropic"

Step 4 - Verify

claude mcp list

All added MCPs should show as connected. If any show disconnected, the token is wrong -- remove and re-add.

What the MCPs expose and do not expose

They expose: client list, GA4 + GSC live data, DataForSEO ranked keywords, Semrush data, Fathom meeting transcripts, BTT WordPress draft management, Screaming Frog crawls, HubSpot CRM.

They do NOT expose: Xero (finances, payroll), HR data (PIPs, contracts), client customer or order or PII data, Aircall recordings, internal Slack DMs.

When tokens are rotated

claude mcp remove
Get the new token from 1Password.
Re-add with claude mcp add --transport http "...new URL..."