Connect Claude to Beeye
Ask about your schedule, budgets and people in Claude. Claude reads your Beeye data with your own access rights and writes the answer. It cannot change anything in Beeye.
This method works in the Claude Desktop app. It does not work in Claude on the web yet: web and mobile follow with sign-in with your Beeye account.
Before you start
- A computer
One where you can install software.
- A Claude account
The free plan is enough for a first test, with low usage limits. For daily use, choose a paid plan.
- Your Beeye API key
In Beeye, click your profile photo, open Informations and click Copy. No key? Ask your Beeye administrator or your Customer Success Manager.
- Your server address
- Europe
https://mcp.eu.mybeeye.com/mcp - Canada
https://mcp.ca.mybeeye.com/mcp - United States
https://mcp.us.mybeeye.com/mcpFrom January 1, 2027
- Europe
- Approval
Your IT or security team approves Claude for Beeye data.
- Extra tools
Claude may need extra tools on your computer to run the connector, such as Node.js (LTS version). Your IT team can install them.
Set it up
- Install Claude Desktop and sign in.
- In Claude Desktop, open Settings > Developer > Edit Config. The file
claude_desktop_config.jsonopens. - Add the Beeye server with the block below. Replace
YOUR_API_KEYwith your key and, outside Europe, the address with your region’s server.claude_desktop_config.json { "mcpServers": { "beeye": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.eu.mybeeye.com/mcp", "--header", "X-BEEYE-API-KEY:YOUR_API_KEY" ] } } }- No space after
X-BEEYE-API-KEY:. - If the file already lists other servers, add only the
"beeye": { ... }block insidemcpServers, separated by a comma. - One missing or extra comma or brace blocks every server. Check the file before you save it.
- Your key stays in this file on your computer. Do not send the file to anyone.
- No space after
- Save the file.
- Quit Claude Desktop completely. On Mac, press Cmd+Q. On Windows, right-click the Claude icon near the clock, then click Quit.
- Reopen Claude Desktop. In Settings > Developer, check that
beeyeshows as running.
Check the connection
In a new conversation, ask: “Am I connected to Beeye?” Allow the Beeye tool when Claude asks. Claude replies with your name and your firm.
Five questions to start
- “Who is overloaded next week, and on which jobs?”
- “Which jobs will go over budget before the end of the fiscal year?”
- “Give me the close-out summary for Aster & Co.: hours, fees and variance to budget.”
- “Who is free in January and has already worked on this client’s audit?”
- “Show utilization by team over the last 3 months, with the 5 jobs most over budget.”
Models and good answers
Beeye tested the connector with Claude Opus 5 and Claude Opus 5.5. Select one of them in Claude: smaller or older models can pick the wrong tool or stop before the answer is complete.
- Give dates: “next week”, “December 2026”.
- Use the exact names of jobs, clients and teams. Say “my jobs” for the jobs you manage.
- If an answer is slow or incomplete, ask for a shorter period or one team.
- Start a new conversation for a new topic: in long ones, the model can mix up details.
- Check important numbers in Beeye before you make a decision.
Troubleshooting
| Problem | What to do |
|---|---|
beeye does not appear in Settings > Developer | Check the commas and braces in the file. Quit Claude Desktop completely, then reopen it. Type node -v to check that Node.js is installed. |
| Claude cannot connect | Check that the address ends with /mcp and matches your region. Check the header name X-BEEYE-API-KEY and that the key has no spaces. |
| Claude says the API key is not valid | Copy the key again from your Beeye profile. If it still fails, contact your Customer Success Manager. |
| Claude shows data you did not expect | Claude uses the access rights of the key’s owner. Check that the file contains your own key. |
| Answers are slow or stop | The request is too large. Ask for a shorter period or a smaller group. |
| A “too many requests” error | Each key can send 60 requests per minute. Wait one minute, then try again. |
Security and your responsibility
- Read-only
Claude cannot create, change or delete anything in Beeye. If it says it changed something, that statement is wrong.
- Your access rights
Claude sees only what your Beeye user can already see.
- A personal key
Your API key is personal: never share it, and never send it by email or in a ticket. If you think someone has it, contact your Customer Success Manager. Beeye revokes it; it can keep working for up to 5 minutes.
- Answers can be wrong
Beeye returns accurate data, but the model writes the answer. It can invent numbers, names or dates, or misread a vague question. Check key numbers in Beeye.
- Usage and cost
One question can make several calls to Beeye and send a lot of data to the model. It counts toward your Claude plan’s usage limits.
- Your firm’s responsibility
Beeye controls the MCP server, not Claude. Your firm decides how Claude is used with Beeye data: the provider’s data, privacy and retention settings, who can see conversations, your policies and the laws that apply, such as GDPR.
Who to contact
| Topic | Contact |
|---|---|
| API key, server, wrong data in Beeye | Your Customer Success Manager |
| Approval to use the assistant with Beeye data | Your IT or security team |
| Claude account, plan or usage limits | Claude support |
| A wrong answer while the data in Beeye is right | No ticket needed: ask again with more detail, or use a tested model |
When you contact Beeye, give the assistant, the model, the question, and the date and time. Never send your API key.
Other guides
- Microsoft CopilotMicrosoft Copilot Studio, then Teams · about 10 minutes
- Other assistantsany assistant that supports MCP · a few minutes
Back to AI connectors: what the assistant can do, governance and FAQ.