AI agents, MCP and API
Here you will learn how to give an AI agent or another app access to Elbuz: through the MCP server, through WebMCP in the browser or through API v2. The agent works with the rights of one employee, and by default its changes wait for your approval in “Pulse”.
- Connect an AI assistant (Claude, ChatGPT, Codex, Cursor) to Elbuz
How to connect an AI assistant to Elbuz over MCP: a key on behalf of an employee, commands for Claude Code, Codex and Cursor, a claude.ai and ChatGPT connector, changes reviewed in Pulse.
- API v2: how to connect your app to Elbuz data
Elbuz API v2 for developers: a Bearer key acting on behalf of an employee, permissions and “Data scope”, filters, cursor, Idempotency-Key, a limit of 120 requests/min, the 202 response and requests in Pulse.
- Legacy Elbuz API (v1): key and moving to API v2
The legacy Elbuz API v1 still works for keys created before 14.10.2026. How to move an integration to API v2, what replaces what, the v1 key fields and how to restrict the key.
