Install the MCP server
Install @lebureau/mcp, get an API key, and wire it into Claude Desktop or Claude Code.
Prerequisites
- Node.js 20 or newer. Verify with
node --version. - A Le Bureau account.
Get an API key
- Sign in to the dashboard.
- Open Settings -- API Keys.
- Click Create API key, give it a descriptive name (for example,
claude-desktop-laptop), and choose its capabilities from the checkbox grid. The default selection is narrow; add more only if you actually need them. - Copy the key immediately. It is shown only once and starts with
sk_live_. Store it in a password manager or your OS keychain. Never commit it to a repository.
If you lose the key, revoke it from the same settings tab and generate a new one.
Run the server via npx
@lebureau/mcp is published on npm. You normally do not run it by hand -- your MCP client launches it for you. The command is:
npx -y @lebureau/mcp@latest
The binary name is lb-mcp. The -y flag accepts the install prompt and @latest ensures you pull the most recent published version on every launch.
Configure Claude Desktop
Open claude_desktop_config.json and add an entry under mcpServers:
{
"mcpServers": {
"lebureau": {
"command": "npx",
"args": ["-y", "@lebureau/mcp@latest"],
"env": {
"LEBUREAU_API_KEY": "sk_live_..."
}
}
}
}
Save the file and restart Claude Desktop. The Le Bureau tools will appear in the next conversation.
Configure Claude Code
Same shape, in .mcp.json at your project root (or in your user-level config):
{
"mcpServers": {
"lebureau": {
"command": "npx",
"args": ["-y", "@lebureau/mcp@latest"],
"env": {
"LEBUREAU_API_KEY": "sk_live_..."
}
}
}
}
Restart Claude Code after saving.
Verify it works
Start a new conversation and ask:
List my desktops.
The assistant should call the desktops_list tool and return your current desktops. If nothing happens, see Troubleshooting below.
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
LEBUREAU_API_KEY | yes | -- | API key from the settings page. Starts with sk_live_. |
LEBUREAU_BASE_URL | no | https://lebureau.talentai.fr | Override only if directed by support. |
LEBUREAU_MCP_LOG_LEVEL | no | warn | One of debug, info, warn, error. Logs are written to stderr. |
LEBUREAU_MCP_DESTRUCTIVE | no | 0 | Reserved for a future release. Has no effect today. |
Troubleshooting
| Symptom | What it means | What to do |
|---|---|---|
401 Unauthorized | The key is invalid or has been revoked. | Generate a new key in Settings -- API Keys. |
403 Forbidden with required and held fields | The key lacks the capability the tool needs. | Either create a new key with the missing capability, or use a different tool. See API capabilities. |
429 Too Many Requests | You hit the per-key rate limit (60 requests per minute). | Wait and retry. The error message includes a Retry-After hint when the server provides one. |
| Tools missing in your MCP client | The client did not pick up the config, or the JSON is invalid. | Restart the client after editing the config file. Validate the JSON -- a stray trailing comma silently drops the entry. |
Related docs
MCP server overview
What @lebureau/mcp is, what it lets your AI assistant do, and how it talks to Le Bureau.
MCP tools reference
The 18 tools shipped in @lebureau/mcp v0.1.0, grouped by area, with the API key capability each one requires.
API capabilities
How API key capabilities work and the seven user scopes you can put on a key.