API keys

API keys connect a local client — Claude Desktop, Cursor, Windsurf, a script — to a workspace, through the Gensy MCP server. You manage them in Settings → AI assistants & API keys, from the Starter plan up.

For Claude.ai, ChatGPT, Claude Code or Cursor, the remote connector is simpler: it doesn’t require a key. A client that doesn’t support OAuth can also use a key with the remote connector, as a header (Authorization: Bearer gsk_…). See the MCP connector page.

Generate a key

1. Open the AI assistants & API keys tab.
2. Give the key a name.
3. Choose the scope: Read + write or Read-only.
4. Choose the expiry: 30 days, 90 days (the default), 1 year or No expiration.
5. Copy the key right away: it’s only shown once.

Any workspace member can generate a key. Up to 5 active keys per workspace (connectors don’t take a slot). A key acts with the role of the person who created it: a member’s key can’t change settings, the brand or fields, bulk-delete employees or invite. It stops working if that person leaves the workspace.

Configure a local client

The tab shows the snippet, ready to copy. For Claude Desktop, it goes in claude_desktop_config.json:

{
  "mcpServers": {
    "gensy": {
      "command": "npx",
      "args": ["-y", "gensy-mcp"],
      "env": {
        "GENSY_API_KEY": "your_key",
        "GENSY_BASE_URL": "address shown in the tab"
      }
    }
  }
}

Restart the client after each change to the file.

Good to know

• A key is tied to a single workspace: data stays isolated.
• A read-only key doesn’t even expose the write tools; any change is refused.
• Limit of 90 requests per minute per key.
• All of a key’s actions appear in Settings → Activity, with “API” as the author.

Active access

The list brings together keys and connectors, with the scope, author, creation date, expiry and last use. Everyone can revoke their own; the owner can revoke everything, and removing a member revokes their access along with them.

My key doesn’t work

• Check that it hasn’t been revoked and hasn’t expired.
• Check that the workspace is on a paid plan: returning to the Free plan revokes keys, and taking a paid plan again doesn’t restore them; you’ll need to create them again. A key also stops working if the person who created it has left the workspace.
• A lost key can’t be recovered: revoke it and generate a new one.