Begin MCP

Connect Claude or ChatGPT to read your workspace and make changes your role allows, such as creating draft shifts, updating people or publishing posts. Begin MCP connects the client to your Begin account through the Model Context Protocol. The connection follows your Begin permissions. It does not grant an AI client administrator access or every feature of the web app.

​

Connect your client

Use https://api.begin.eu/mcp as the remote MCP server URL. Add it where your client accepts a custom or remote MCP server, sign in with your Begin account when the client opens the authorisation page, then approve the connection. Each client documents its own steps and who in an organisation may add a server:

• Claude: custom connectors guide.
• ChatGPT: developer mode for individual accounts, apps in managed workspaces for Business, Enterprise and Edu.
• Claude Code: run claude mcp add --transport http begin https://api.begin.eu/mcp, then /mcp to sign in.

​

Check the workspace and ask

The connection is pinned to whichever Begin workspace is active on its first use. Switching workspace later in the web app does not move an existing connection. Ask the client which workspace it is connected to before asking it to make changes. Spell people and place names as Begin spells them. For calculated hour totals, use the timesheet in Begin. MCP can read time entries, but adding their durations does not reproduce Begin’s calculated timesheet summary.

​

Approve changes after the client reads others’ words

Some answers carry text another person in the workspace wrote, such as a position name, a comment or a message. That text could try to steer your client. Once your client has read such text, everyday changes still apply straight away: posts and comments, positions, locations, departments, labels, clients, draft shifts, documents, and your own inbox and follows. Your client’s own tool permissions decide those. Every other change waits for you under Settings → Security → Changes waiting for your approval, including deletions, imports, messages, publishing shifts, leave, time entries, automations, changes to people, pay, approvals, policies or settings, and any everyday change that removes something, acknowledges a compliance rule or shows a post to more people. Each change shows what it is, what it is about and which client sent it. Choose Approve or Reject. An approved change runs as sent, with the access you have at that moment. A change nobody approves within a day is dropped. Your client is told the change is waiting and can ask Begin later whether it ran. Approve only changes you asked your client for. Revoking the client rejects everything it left waiting, and a new connection starts without the wait until it reads such text again.

​

Attach a file from your computer

Ask the client to attach a local file to a post or a Docs page and it sends the file with the request, so you do not have to publish it online first. Images, PDFs and office documents are accepted; Begin refuses programs and scripts. One file sent this way can be up to 10 MB. For anything larger, upload it in Begin, or give the client an address the file is already published at.

​

Revoke or change the connection

Open Settings → Security → Connected MCP clients to check a connection’s workspace and last activity, revoke one client, or revoke all clients. To use another workspace, switch to it in Begin, revoke the existing connection, and reconnect from your client. Its first use pins it to the new workspace. An administrator switching off Begin AI for the workspace also stops MCP access. Permission changes apply to subsequent requests. When access stops this way, your client reports an error rather than asking you to sign in again, and signing in again will not restore it. Put the access back in Begin first: rejoin or reactivate the membership, or have an administrator switch Begin AI back on. Then retry from the client.

​

Next

​

Still need help?