Beta

Connect AI assistants to Superteams

Overview

Superteams works as an MCP server (Model Context Protocol), so AI assistants like Claude and Cursor can search and read your team's processes and answer from them, instead of giving generic advice.

Setup takes four steps:

  1. An admin turns on access for the workspace (once).
  2. Each person creates a personal token.
  3. They add Superteams to their assistant with that token.
  4. They ask questions as usual.

Supported today: Claude Code, Cursor, Claude Desktop and any client that can send an Authorization header. One-click connectors for claude.ai and ChatGPT are coming soon.

1. Turn on access (admins)

Access is off by default. Only workspace owners and admins can turn it on.

  1. 1Click your name at the bottom of the sidebar and choose AI assistants.
  2. 2Read What turning this on means and tick the confirmation box.
  3. 3Click Turn on.
superteams.eu/acme/settings/ai

Personal

Profile
Notifications
AI assistants1

AI assistants

Let Claude, ChatGPT, Cursor and other assistants answer from your team's processes.

Settings → AI assistants, in the Personal section.
Settings → AI assistants

Workspace access

Off. Nobody in this workspace can connect an assistant.

Off

What turning this on means

Turn on3
Confirm (2) and turn on (3). The badge changes to On.

Pages are encrypted at rest. To answer, Superteams decrypts the pages an assistant asks for and sends their text to that assistant's AI provider (for example Anthropic or OpenAI), under that provider's terms. Check that this fits your company's policies before turning it on.

2. Create your token

A token connects one assistant to this workspace as you: it sees exactly the published pages you can see. Create one per tool, so you can revoke them separately.

  1. 1In Settings → AI assistants → Your access tokens, give the token a name you'll recognise (e.g. “Claude Code on my laptop”).
  2. 2Click Create token.
  3. 3Copy the token now. For your security it is shown only once. The setup commands for each assistant appear right below it, ready to copy.
Settings → AI assistants

Your access tokens

Claude Code on my laptop1
Create token2

Token created

Copy it now. It won't be shown again.

st_Q2x8…••••••••••••••••3
Name (1), create (2), copy (3). Tokens start with st_.

Treat the token like a password: don't paste it in chats, tickets or shared files. If it leaks, revoke it and create a new one.

3. Connect your assistant

Your workspace's MCP address is:

https://www.superteams.eu/api/mcp

Claude Code

  1. 1In a terminal, run (replace st_… with your token):
claude mcp add --scope user --transport http superteams https://www.superteams.eu/api/mcp --header "Authorization: Bearer st_…"

--scope user makes Superteams available in every folder. Without it, it only works in the folder where you ran the command.

  1. 2Start claude and type /mcp. Superteams should show as connected, with 4 tools.
Terminal
1

$ claude mcp add --transport http superteams https://www.superteams.eu/api/mcp --header "Authorization: Bearer st_…"

Added HTTP MCP server superteams

2

$ claude

> /mcp

MCP servers

superteams ✔ connected · 4 tools

Add the server (1), then check it with /mcp (2).

Cursor

Open ~/.cursor/mcp.json (or .cursor/mcp.json in a project), add the block below and save. Cursor picks it up under Settings → MCP.

{
  "mcpServers": {
    "superteams": {
      "url": "https://www.superteams.eu/api/mcp",
      "headers": {
        "Authorization": "Bearer st_…"
      }
    }
  }
}

Claude Desktop

Claude Desktop reaches remote servers through the mcp-remote bridge, which needs Node.js installed. Open Settings → Developer → Edit config, add the block below to claude_desktop_config.json, save and restart Claude Desktop.

{
  "mcpServers": {
    "superteams": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.superteams.eu/api/mcp",
        "--header",
        "Authorization: Bearer st_…"
      ]
    }
  }
}

4. Ask questions

Ask as you normally would. The assistant decides when to search Superteams, reads the relevant pages and cites them. The first time it uses each tool, it may ask for your permission.

  • “How do we run the month-end close?”
  • “What do I need to do before a new hire's first day?”
  • “Search Superteams for everything about holiday requests.”
  • “Which areas exist in Superteams?”
Claude
How do we run the month-end close?
superteams · search_pages“month-end close”superteams · get_page“Month-end close”

Your team closes the books in 5 working days. In short:

  1. WD 1: invoices posted, bank reconciled
  2. WD 2–3: accruals and balance sheet reconciliations
  3. WD 4–5: review, sign-off, period locked

Source: Finance / Month-end close

The assistant searches, reads the page and answers with the source.

Tip: mention “Superteams” in your question when you want the assistant to use your documented process rather than general knowledge.

What assistants can do

Access is read-only. Assistants can't edit, publish or delete anything.

ToolWhat it does
search_pagesSearches published pages by title and content, optionally in one area.
get_pageReads one page in full, with its area, publish date and link.
list_areasLists the areas you can see.
list_pagesShows the pages of one area as a tree.
  • Only **published** pages. Drafts, and unpublished edits to published pages, are never shared.
  • Only pages **you** can see: area permissions apply exactly as in the app.

Manage, audit and security

  • **Revoke a token:** Settings → AI assistants → Your access tokens → Revoke (click twice to confirm). It stops working immediately.
  • **Turn off for everyone (admins):** Workspace access → Turn off. All tokens stop working at once.
  • **Leaving the workspace:** a person's tokens stop working as soon as they're removed.
  • **Activity log (admins):** every request is recorded with who, which tool and which page. Search terms are not stored.
  • **Limits:** 60 requests per minute per token; very long pages are truncated for the assistant.
  • **AI credits:** assistant requests don't use your workspace's AI quota.
Settings → AI assistants

Recent activity

WhenWhoActionPage
10:42Anaget_pageMonth-end close
10:42Anasearch_pages3 results
09:15Ruilist_areas—
Recent activity, visible to admins on the same page.

Troubleshooting

What you seeWhat to do
401 · invalid or revoked tokenCreate a new token and update your assistant's config.
403 · access turned offAsk an admin to turn on Workspace access.
Server shows as failed / not connectedCheck the address and that the header reads exactly “Authorization: Bearer st_…”. Restart the assistant.
A page isn't foundIt may be a draft, or in an area you can't see. Publish it or check area permissions.
Rate limit reachedWait a minute; the limit is 60 requests per minute per token.