Keys and connectors
Set up Claude with the sign-in connector, or Claude Code with an Infra key. Manage and revoke what you created.
All connections are managed on Knowledge Base › Connections. The page has two tabs:
- Infra to agents: connect Claude to Infra, and manage your keys.
- Connectors to Infra: connect Granola and Microsoft 365, so the project agent can bring sources into a project.
Connect Claude (sign-in connector)
Under Use Infra from your AI assistant, pick Claude.
Copy the connector URL
Click Copy the connector URL.
Add it in Claude
In Claude: Settings → Connectors → Add custom connector. Name it BHG Infra, paste the URL and click Add. The desktop app has the same menu.
Sign in and choose access
Enter your @bluehorizonsgroup.com email and the 8-digit code Infra emails you. Then choose what the assistant may change. Everyday changes is a good start.
What you tick when you sign in limits what the assistant may change, on top of your role. The groups include everyday deal changes, leads and contacts, Plans, approval requests and vendor risk, Final decisions (closing deals, approvals and overrides) and Admin settings. A tool refused with write_group_not_granted needs its group: remove the connector, add it again, and tick that group.
Good to know:
- The code lasts 10 minutes. No code? Look in Junk, wait a minute, then resend.
- You stay signed in for 14 days, then sign in again.
- "Trouble connecting": check the URL was pasted exactly, with nothing after it.
For agents that stage project changes or add project documents, use an Infra key: a key made for An engagement, with Write ticked. Ask the agent to call edge_whoami to see what a connection can do.
Connect Claude Code (Infra key)
Pick Coding tools, then Claude Code.
Create a key
Click Create a key. Choose what the key is for under What is this key for?:
- An engagement: one client and every project under it. Refused everywhere else, on reads as well as writes. Tick Write to create, edit and archive knowledge and stage project changes.
- Publishing to the knowledge base: Propose queues pages for an admin to approve; Publish (admins only) sends them live.
- General automation: everyday Infra writes. Tick Write for state-changing requests.
- Read-only: fetch anything you can already see. Changes nothing.
Give it a Name (for example "Claude Code — laptop") and an Expires period (30 days, 90 days or 1 year). Click Create key.
Copy the key now
The key is shown once. Copy it and keep it like a password: it authenticates as you.
Add it to your tool
Under Connect a coding tool, pick Claude Code. Right after you create a key, the steps are shown with it filled in. Otherwise paste your key where it says <your edge_sk_ key>.
Claude Code sends the key as Authorization: Bearer edge_sk_… to the server URL shown under Advanced › Connection details. The server's name is bhg-edge.
Set up a whole repo
Advanced › Set up Infra for a whole project gives a .mcp.json to commit to a repo. It reads each person's own key from the EDGE_API_KEY environment variable, so no key is ever committed.
Manage keys
Your keys are listed on the same page, with what each can reach ("Everything you can reach", or the engagement it is limited to). You can have up to 10 active keys. Revoke a key there when you no longer need it, or if it may have leaked. Keys expire; there is no "never".
An unscoped key follows your access: if you join a new client later, the key reaches it too. An engagement key stays limited to that engagement.
Connect Granola and Microsoft 365
On Connectors to Infra:
- Granola: meeting notes and transcripts from your Granola account.
- Microsoft 365: Outlook email, your calendar, Teams meeting transcripts, and SharePoint or OneDrive files, read as you.
Click Connect and sign in. Once connected, the card shows the account; Disconnect removes it. The project agent can then copy a meeting, email or file onto a project for you. See Knowledge tab.