Connect Claude to Platform Data (MCP)

Let Claude Code or Claude Desktop read live platform data (shifts, staff meals, pricing, and more) through the MCP server. A one-time setup that your Claude does most of.

Overview

The platform runs an MCP server — a secure bridge that lets your Claude (Claude Code or Claude Desktop) read live data from the platform: shifts, staff meals, recruiting/HR, pricing, and more. Once it is connected, you can simply ask your Claude things like "show me this month's shifts" and it pulls the real numbers.

This is a one-time setup, and most of it can be done by your Claude. You only do a couple of things by hand — mainly: get a token (usually by asking an admin), and (for Claude Desktop) restart the app.

For most people the MCP is read-only. Changing data (e.g. editing shifts or meals) is limited to admins.

Throughout this page:

• 🤖 = a step you can hand to your Claude (copy the prompt).
• 👤 = a step only you can do by hand.

Before You Start

If you plan to use Claude Desktop, check Node.js first:

Step 1 — Get Access (ask an Admin) 👤

By default, most people don't have access to the MCP token page, so the first step is usually to ask an administrator. There are two ways:

Option 1 (easiest) — ask an admin to issue a token for you. An admin can create a token on your behalf and send you the mcp_… string. Tell them what you need it for (which data), so they can pick the right scopes. Treat the token like a password — it's shown only once.

Option 2 — ask an admin to grant you MCP access, then issue it yourself. Once an admin grants your account the "mcp" app, open https://mcp.algoritmigroup.com/ → My MCP Tokens → Issue new token, set a label and the scopes you need, then copy the token (shown only once).

Scopes = what your Claude may access. For reading, pick the read scopes you need (e.g. shifts, staff meals). Write access is admin-only. Scopes can be changed later without re-issuing the token.

Who to ask — these staff are current administrators:

Whichever way you get it, keep the token private — never paste it into shared chats or commit it to code.

Step 2 — Connect

Use the client you actually work in. Claude Code is the simplest.

Option A — Claude Code (recommended)

Paste your token into this prompt and hand it to Claude Code:

Or run it yourself in a terminal:

claude mcp add --transport http --scope user algoritmi-vibe https://mcp.algoritmigroup.com/api/mcp --header "Authorization: Bearer mcp_YOUR_TOKEN_HERE"

Then check it worked: in Claude Code, type /mcp. You should see algoritmi-vibe connected, with a list of tools.

Option B — Claude Desktop

Claude Desktop needs a small bridge (mcp-remote). The easiest way is to let Claude Code write the config file for you:

Then, by hand: fully quit and reopen Claude Desktop 👤 so it loads the new config. In the chat box, open the tools (slider) menu — the algoritmi-vibe tools should appear.

Manual fallback — the exact config to paste yourself:

{
  "mcpServers": {
    "algoritmi-vibe": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.algoritmigroup.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer mcp_YOUR_TOKEN_HERE" }
    }
  }
}

Tip: the same ready-to-copy config is shown on the MCP site's home page under "Claude Desktop / Cursor config".

Step 3 — See What You Can Access

What you can do depends on the scopes on your token, which differ from person to person. Rather than guessing, ask your Claude to tell you — using real data:

Your Claude will list the tools your token unlocked and show a real example. If it reports no matching tools or a permission error, see the troubleshooting table below.

If Something Doesn't Work

Who Does What

Quiz