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.
- Find Connectors (or Custom Connectors / Custom MCP).
- Click Add custom connector.
- Paste the URL from one of the cards above (use the
/sseform when prompted: e.g.https://northbeam-mcp.shane-862.workers.dev/sse). - For the auth header, enter: Authorization: Bearer <token> using the token shown above.
- Save. Repeat for each connector you want access to.
Don't see custom connectors? Ask Shane or your workspace admin to enable it.
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",
"--header", "Authorization: Bearer nb-mcp-auth-mudwtr-2026"
]
}
Same pattern for the others — swap the URL and the bearer token.
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 bearer tokens above are not the API keys. They're access passwords for our workers. Treat them like internal passwords — 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.