Connect Siggmund to your AI assistant (MCP)

What it is for

MCP (Model Context Protocol) is a standard that lets an AI assistant such as Claude consult an external service. Once Siggmund is connected, you ask your assistant questions in plain language and it reads your Siggmund measurements to answer: where you stand, what has changed since last week, who is ahead of you.

Access is read-only and limited to your own data. Your assistant cannot change anything at Siggmund, generate a report, or see another client.

Before you start: create a key

Organisation admins can create a key. If you are not comfortable with a terminal or a configuration file, pass this guide on to the person who manages your tools.

1. Open Connections in the menu, then the MCP access section.
2. Open the MCP access keys card and give the key a name, for example "Marie's Claude".
3. Choose how long it lives: 1 day, 1 week, 1 month, 1 year, or no expiry.
4. Click Create key and copy it. It starts with shg_.

The key is shown only once. Siggmund does not keep its value: if you lose it, create another one.

What you need

• The server address: https://mcp.siggmund.com/mcp (if you configured the old run.app address, it remains valid)
• Your key, sent in an HTTP header: Authorization: Bearer shg_…

Replace shg_… with your key in the examples below.

In Claude Code

In a terminal, run:

claude mcp add --transport http siggmund https://mcp.siggmund.com/mcp \
  --header "Authorization: Bearer shg_…"

To make the connection available in all your projects, add --scope user before the address. Without it, the connection only applies to the current folder.

Then check: claude mcp list should show siggmund as "Connected". Inside Claude Code, the /mcp command shows the same status. A failure with a 401 code means the key is wrong, revoked or expired.

In Claude Desktop

The Connectors menu of Claude Desktop has no field for a key, so Siggmund is plugged in through the configuration file, using the small mcp-remote bridge. It requires Node.js to be installed.

1. In Claude Desktop, open Settings, the Developer tab, then click Edit Config. The claude_desktop_config.json file opens. It lives in ~/Library/Application Support/Claude/ on macOS and in %APPDATA%\Claude\ on Windows.
2. Add the siggmund block (keep your other servers if you have any):

{
  "mcpServers": {
    "siggmund": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.siggmund.com/mcp",
        "--header",
        "Authorization:${SIGGMUND_AUTH}"
      ],
      "env": {
        "SIGGMUND_AUTH": "Bearer shg_…"
      }
    }
  }
}

3. Save, then quit Claude Desktop completely and start it again.
4. In the input box, open the Connectors menu: siggmund should be listed with its tools.

The missing space after Authorization: is intentional: it stops Windows from splitting the value in two. The key sits in the env entry, not in the command line.

In Cursor (or another compatible client)

Cursor can send a header directly, no bridge needed. In ~/.cursor/mcp.json (all your projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "siggmund": {
      "url": "https://mcp.siggmund.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SIGGMUND_KEY}"
      }
    }
  }
}

Set the SIGGMUND_KEY environment variable to your key (without the word Bearer), then restart Cursor.

For any other MCP client: choose a remote server over HTTP transport ("Streamable HTTP"), enter the address above and add the header Authorization: Bearer shg_….

Questions to ask

Your assistant picks the right tool by itself. Here are questions Siggmund can answer today, and what the assistant reads.

You can also ask for a cross-tab of your figures (for example "rank my entry points from lowest to highest score"): the assistant then queries your data directly.

What the MCP does not do with this type of key: produce a report or a presentation, write to our support team, or change your account.

Security

• The key is shown only once. Copy it into your tool as soon as it appears. It cannot be retrieved or sent to you by e-mail.
• Do not share it, and do not paste it into a shared document, an e-mail or a code repository. One key per person or per tool lets you cut one access without affecting the others.
• Pick a short lifetime if you do not need permanent access. An expired key is refused from the next call.
• Revoke it at any time in Connections, MCP access section, with the key's revoke button: access is cut immediately. Do it as soon as you suspect it has leaked.
• The key only gives access to your organisation, read-only.

If it does not work

• 401 or "Failed to connect": the key was copied wrongly, revoked or expired. Check the list in Connections and create a new one if needed.
• The server does not show up in Claude Desktop: is Node.js installed? Did you quit the app completely before restarting it? The configuration file must be valid JSON (commas, quotes).
• Slow first call: the service can take a few seconds to wake up. Try again.
• The assistant finds no Siggmund tool: check that the server is enabled in your assistant's settings, and explicitly ask it to use Siggmund.

Last updated: October 26, 2026 · First published: October 26, 2026