You can connect GitHub Copilot to Albacross and ask it about the companies visiting your website, in VS Code or in Copilot CLI in your terminal. For example: "Which companies from Germany looked at our pricing page this week?" or "What has Acme done on our site in the last 30 days?"
Before you start
GitHub Copilot in VS Code, or Copilot CLI (
npm install -g @github/copilot).On Copilot Business or Enterprise, an admin of your GitHub organization has to allow MCP servers: Settings > Copilot > Policies, MCP servers in Copilot. If your organization only allows servers from its MCP registry, the admin has to add Albacross there too.
AI clients turned on for your Albacross workspace. They're in beta: ask your account manager or Albacross support.
CRM data and contacts are off until an Owner or Admin of your Albacross workspace allows them. If you want them, ask before you connect, or you'll have to connect again later. See How do I manage AI clients for my Albacross workspace?
Add Albacross
VS Code and Copilot CLI read the same settings file, so adding Albacross once makes it available in both. Open ~/.copilot/mcp-config.json (create it if it isn't there) and add:
{
"mcpServers": {
"albacross": {
"type": "http",
"url": "https://mcp.albacross.com/mcp",
"tools": ["*"]
}
}
}
If the file already lists other servers, add the "albacross" entry next to them inside "mcpServers".
In VS Code you can also run MCP: Add Server from the Command Palette, pick HTTP, and enter https://mcp.albacross.com/mcp as the URL and albacross as the name.
To share it with your team in VS Code, put the same content in a file called .mcp.json at the root of a project. Everyone who opens the project still signs in with their own Albacross login.
Sign in
1. Start the sign-in. In Copilot CLI, start copilot: it opens Albacross in your browser, and if it doesn't, run /mcp auth albacross. In VS Code, click Authenticate or confirm the sign-in when VS Code offers it for Albacross.
2. Sign in to Albacross, the same way you sign in to the app. The page says Connect github.com to Albacross, because Copilot signs in as github.com. Older VS Code chat sessions show vscode.dev instead.
3. Pick the workspace Copilot should read. One connection reads one workspace.
4. Tick the CRM box if you want Copilot to see CRM data, and the contacts box if you want it to see the people at a company. Then click Allow.
Only click Allow if you started connecting in Copilot yourself. If someone sent you the link, click Cancel.
If none of your workspaces can be picked, AI clients aren't turned on for them, or your role can't see companies.
5. Go back to VS Code or your terminal. Copilot may ask before it uses an Albacross tool. The tools only read, so you can allow them.
Try it
Ask Copilot, and change the details to fit your business:
"Using Albacross, which companies visited us in the last 7 days? Show me the 10 most active."
"Using Albacross, what has Acme looked at on our website in the last 30 days, and who works in marketing there?" The people part needs contacts: allowed for the workspace and ticked when you connected.
Copilot can do the same things as Claude, with the same CRM data, contacts and limits. See How do I connect Claude to Albacross? for what it can read, more prompts and tips.
See and disconnect
Go to Settings > Personal Security > Connected AI clients. Copilot shows as GitHub Copilot, or VS Code for older VS Code chat sessions. Disconnect ends the connection after you confirm, and Copilot then asks you to sign in again.
Removing Albacross from mcp-config.json does not end the connection in Albacross. Disconnect it there too.
A connection also ends when you change or reset your Albacross password, when it isn't used for 30 days, or 90 days after you made it. Copilot then asks you to sign in again.
