Internal Setup Guide
Custom MCP Connectors
Five remote MCP servers running on Cloudflare. Anyone on the team can connect to these from Cowork or Claude Code to pull data into reports without setting up local API keys.
The Connectors
What's Available
Setup
Adding to Cowork
- Open Cowork → click your avatar → Settings → Connectors.
- Click Add custom connector.
- Enter a Name (e.g. "Northbeam") and paste the URL from one of the cards above.
- Skip Advanced settings — leave OAuth Client ID / Secret blank. The access token is already in the URL.
- Click Add. Repeat for each connector you want.
Don't see "Add custom connector"? Workspace admin needs to enable it. Ping Shane.
Setup
Adding to Claude Code (CLI)
If you use Claude Code in the terminal, add this to your ~/.mcp.json (one block per connector):
"northbeam": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://northbeam-mcp.shane-862.workers.dev/sse?token=nb-mcp-auth-mudwtr-2026"
]
}
Same pattern for the others — swap the URL.
Notes
Good to Know
- API keys are server-side. Each worker holds the upstream API credentials as encrypted secrets. You never paste API keys yourself — just the worker URL and the bearer token.
- The token in the URL is not the API key. It's an access password for our worker. Treat the URL like an internal password — fine within the team, don't share publicly.
- Cloud connectors (Asana, Notion, Slack, Gmail, Google Drive, Northbeam, Supermetrics, Omni, Box, etc.) are separate — those are added through Cowork's standard connector marketplace and authenticated with each person's own login.
- Issues? Ping Shane on Slack. URLs that 401 mean a wrong bearer token; 500s mean the upstream API is having a moment.