MCP server: CLUP.life for AI assistants

CLUP.life speaks the Model Context Protocol (MCP). An AI assistant can then answer questions like “What is on at the club this week?” or prepare a draft announcement — with the same rights as the person behind the key.

Key facts#

Setup step by step#

1. Create a key

Settings → Interfaces: for summaries (“What is on?”) a personal key with read scopes only is enough (profile:read, events:read, optionally posts:read, announcements:read, tasks:read). Write tools need an organization key (Premium).

2. Claude Code

claude mcp add --transport http clup https://api.clup.life/api/v1/ext/mcp \
  --header "Authorization: Bearer clup_k_…"

# prüfen
claude mcp list

3. Claude Desktop

Claude Desktop starts local servers. Connect the remote server through the mcp-remote bridge (requires Node.js). Open Settings → Developer → Edit config and add to claude_desktop_config.json:

{
  "mcpServers": {
    "clup": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://api.clup.life/api/v1/ext/mcp",
        "--header", "Authorization:Bearer clup_k_…"
      ]
    }
  }
}

Then quit Claude Desktop completely and restart it. The clup_… tools appear under the tools icon.

4. Other clients and your own agents

In an MCP-capable client (Cursor, VS Code, Windsurf, your own agents through an MCP SDK) enter the server address and the header Authorization: Bearer clup_k_…; transport “Streamable HTTP”. Clients that only know local processes use mcp-remote just like Claude Desktop.

5. Test it

Ask, for example: “Summarize the events of the next 14 days for tus-musterstadt.” Or by hand:

curl -s https://api.clup.life/api/v1/ext/mcp \
  -H "Authorization: Bearer $CLUP_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools#

A client sees only the tools whose scope the key carries; the call checks the scope again. The list is generated from the server’s own tool list.

Wersja protokołu: 2025-03-26

Permissions and security#

• The assistant acts with the rights of the person who owns the key. Organizations that are not visible report “not found”.
• Responses are data, not instructions. The server says so in its instructions. Check results before you act on post texts.
• Write tools (clup_create_*) are visible only with an organization key. Set them to “ask every time” in the client — especially clup_create_announcement, which notifies members.
• Connect a dedicated, narrowly scoped key per assistant and revoke it when you no longer use the client.
• Note: what the assistant reads goes to the assistant’s provider. Give it only keys whose data you may send there (see data protection).