Skip to content

Application Development

Superblocks MCP connector

The Superblocks connector brings your Superblocks users and groups into Elaichi, so Claude, ChatGPT, Cursor, or any MCP client can look up, add, update, and remove people and group memberships in Superblocks under your own access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Superblocks to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Superblocks once

  1. Open Connections, choose Add connection, and pick Superblocks.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Superblocks API key. One person generates a token in Superblocks and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

superblocks
Superblocks
Apache Airflow
Boomi
Browserbase
Caspio
Cloudflare
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Superblocks to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Superblocks to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Superblocks to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Superblocks to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Superblocks through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • IT

    Set up a new hire in Superblocks

    Create the person's Superblocks account and drop them into the right groups on their first morning, without opening the admin console.

  • IT

    Offboard a leaver the same day

    Find everyone who left this week, remove them from their Superblocks groups, and deactivate or delete their accounts in one pass.

  • Security

    Check who can reach Superblocks

    Ask for a full list of Superblocks users and the groups each belongs to, then flag anyone who should not be there.

  • Operations

    Move a whole team into a new group

    Create a Superblocks group for a reorganized team and add every member at once instead of one by one.

  • People

    Keep names and titles current

    After a promotion or a name change, update the person's Superblocks record so it matches the HR system.

  • Compliance

    Answer an access review question

    Pull the members of a sensitive Superblocks group and hand the auditor a list with every change traceable in the log.

Try asking

  • “List all Superblocks SCIM groups and their member counts.”
  • “Which Superblocks SCIM users were created in the last 14 days?”
  • “Add the new joiner to the Superblocks engineering SCIM group.”

See all 16 Superblocks tools below

AI tools

Superblocks tools for your AI agents

16 tools are ready to call through Elaichi's MCP endpoint the moment you connect Superblocks, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Superblocks gets you

6 screens from the product, each doing one job for your Superblocks account.

The agent

Ask about Superblocks SCIM users in plain language.

Starter prompts read live Superblocks users and groups and answer in seconds.

  • users
  • groups
  • resource types
  • service provider configs

Ask Elaichi to work across your apps.

List all Superblocks SCIM groups and their member counts.

Which Superblocks SCIM users were created in the last 14 days?

Add the new joiner to the Superblocks engineering SCIM group.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect Superblocks from any MCP client over OAuth, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

16 Superblocks tools are ready without custom code.

Browse every Superblocks SCIM user, group and resource type tool with its methods.

  • List all Superblocks SCIM users
  • Create a Superblocks SCIM user
  • Get single Superblocks SCIM user by ID
  • Update a Superblocks SCIM user by ID
ElaichiTools
Tool Action Description
List all Superblocks SCIM users List List Superblocks SCIM users in your organization. Returns: id, schemas, userName, displayName, emails, name, active, groups, role. Results are extracted from the SCIM Resources array.
Create a Superblocks SCIM user Create Create a new Superblocks SCIM user in your organization. Returns: id, schemas, access_token, token_type, expires_in. Required: emails, and at least one name attribute or displayName.
Get single Superblocks SCIM user by ID Get Get a single Superblocks SCIM user by id. Returns: id, schemas, access_token, token_type, expires_in. Required: id.
Update a Superblocks SCIM user by ID Update Update a Superblocks SCIM user's profile by id, including display name, email, groups, active status, and organization role. Returns: id, access_token, token_type, expires_in. Required: id.
Delete a Superblocks SCIM user by ID Delete Deactivate a Superblocks SCIM user by id. Deleting a user through SCIM deactivates them from the organization. Returns an empty 204 response on success. Required: id.

Toolboxes

Every team gets its own Superblocks toolbox.

Toolboxes scope Superblocks SCIM tools to the team that actually needs them.

  • IT Operations
  • Security
  • Platform Engineering
  • People Operations
ElaichiToolboxes
Name Source template Tools Created

IT Operations toolbox

Superblocks · users and provisioning

Superblocks starter 18 Mar 4, 2026

Security toolbox

Superblocks · group membership reviews

9 Mar 2, 2026

Platform Engineering toolbox

Superblocks · groups and resource types

24 Feb 27, 2026

People Operations toolbox

Superblocks · joiners and leavers

Superblocks starter 6 Feb 19, 2026

Internal Tools toolbox

Superblocks · app access by group

31 Jan 30, 2026

Support toolbox

Superblocks · read only user lookups

12 Jan 22, 2026

Shared connections

Teammates use Superblocks without seeing a credential.

Each connection shows who linked the Superblocks account and which teams and members share it.

  • IT Operations
  • Security
  • Platform Engineering
  • People Ops
ElaichiConnections
Connection Scope Status Access
SU

Superblocks (IT Operations)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
SU

Superblocks (Security)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
SU

Superblocks (Platform Engineering)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
SU

Superblocks (People Ops)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
SU

Superblocks (Internal Tools)

Connected by Clara Nowak

Personal • Active Not shared
SU

Superblocks (Support)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Superblocks call has a name attached.

When, who, what happened, type and resource for each Superblocks SCIM action.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Superblocks Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Superblocks Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Superblocks Users List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and Superblocks work finishes itself.

Fetch SCIM users, group them, draft a digest, approve, then post back to Superblocks.

Superblocks digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch users

    Superblocks

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Superblocks

    Queued

Collections and dashboards

Superblocks SCIM numbers arrive before anyone asks.

Four metrics, 14 days of users created and a team breakdown, refreshed on schedule.

Superblocks health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Groups

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

IT Operations 34%

Security 27%

Platform Engineering 21%

People Ops 18%

FAQ

Frequently asked questions

How do I connect Superblocks to Claude?

In Elaichi, choose Superblocks and paste in a Superblocks API key; that is the whole sign-in step, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with Superblocks as you.

Does Superblocks work with ChatGPT and Cursor as well as Claude?

Yes. Once Superblocks is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi agent. You connect Superblocks once and every client picks it up.

What can an AI agent actually do with my Superblocks data?

With Superblocks connected, an agent can list the people and groups in your Superblocks organization, look up a single person, add a new user, change their details, and remove them. It can also create groups, edit who is in them, and handle a batch of these changes in one go, so onboarding a team or clearing out leavers becomes a request in plain language rather than a session in the admin console.

Does connecting Superblocks give the AI access to every user and group?

Only what the person who connected Superblocks can already see and change. The Superblocks API key you paste carries its own permissions, and every call runs inside them. Elaichi can narrow that further with restrictions, but it can never grant anything the Superblocks account itself does not have.

Can my team share one Superblocks connection?

Yes. One administrator connects Superblocks in Elaichi and shares the connection with a team, and nobody else ever sees or handles the Superblocks API key. Each teammate still signs in to Elaichi as themselves, so every change to a Superblocks user or group is logged under the name of the person who asked for it.

Can I stop an agent from deleting or changing things in Superblocks?

Yes. Restrictions in Elaichi apply per action, so you can allow listing and looking up Superblocks users and groups while blocking deletes, updates, or bulk changes. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.

What happens to a Superblocks connection when someone leaves?

When you offboard a person in Elaichi, their access to Superblocks through Elaichi ends immediately across every client. If they were using a shared Superblocks connection, it keeps working for everyone else on the team. If you need to remove Superblocks entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Superblocks in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.