# 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. Source: https://elaichi.ai/connectors/superblocks/ ## Facts | | | | --- | --- | | Application | Superblocks | | Category | Application Development | | AI tools | 16 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Superblocks is connected - 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. ## Connect Superblocks in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Superblocks. 2. Optionally set Share with, 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Superblocks tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Superblocks to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Superblocks to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Superblocks tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Superblocks through Elaichi ### Set up a new hire in Superblocks IT. Create the person's Superblocks account and drop them into the right groups on their first morning, without opening the admin console. ### Offboard a leaver the same day IT. Find everyone who left this week, remove them from their Superblocks groups, and deactivate or delete their accounts in one pass. ### Check who can reach Superblocks Security. Ask for a full list of Superblocks users and the groups each belongs to, then flag anyone who should not be there. ### Move a whole team into a new group Operations. Create a Superblocks group for a reorganized team and add every member at once instead of one by one. ### Keep names and titles current People. After a promotion or a name change, update the person's Superblocks record so it matches the HR system. ### Answer an access review question Compliance. Pull the members of a sensitive Superblocks group and hand the auditor a list with every change traceable in the log. ## 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. ## All 16 Superblocks tools Every tool below is callable through https://api.elaichi.ai/mcp once Superblocks is connected, subject to the toolbox it is in and the restrictions on the caller. - **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. - **Superblocks SCIM users partial update** (Update). Partially update a Superblocks SCIM user by id via PATCH — used to deactivate or reactivate users and push profile attribute changes. Returns the updated user with id, emails, displayName, name, groups, active, and role. Required: id. - **List all Superblocks SCIM groups** (List). List Superblocks SCIM groups. Returns: schemas, id, displayName, members, meta. - **Create a Superblocks SCIM group** (Create). Create a Superblocks SCIM group. Groups and their members can be pushed from an identity provider. Returns: schemas, id, displayName, members, meta. Required: displayName. - **Get single Superblocks SCIM group by ID** (Get). Get a single Superblocks SCIM group by id. Returns: schemas, id, displayName, members, meta. Required: id. - **Update a Superblocks SCIM group by ID** (Update). Update a Superblocks SCIM group by id, including renaming the group and managing member assignments. Returns: schemas, id, displayName, members, meta. Required: id, displayName. - **Delete a Superblocks SCIM group by ID** (Delete). Delete a Superblocks SCIM group by id. Returns an empty 204 response on success. Required: id. - **Superblocks SCIM groups partial update** (Update). Partially update a Superblocks SCIM Group by applying PATCH operations to assign or unassign users from the group. Returns the updated group including id, displayName, and members. Required: id. - **List all Superblocks SCIM service provider config** (List). Get the Superblocks SCIM 2.0 service provider configuration. Returns: schemas, documentationUri, patch, bulk, filter, changePassword, sort, etag, authenticationSchemes. - **List all Superblocks SCIM resource types** (List). List SCIM resource types available in the Superblocks SCIM API. Returns resource type definitions including id, name, description, endpoint, and schema for each supported resource type. - **List all Superblocks SCIM schemas** (List). List SCIM 2.0 schema definitions supported by the Superblocks SCIM API. Returns: id, name, description, attributes.givenName, name.familyName, groups, active, and role (urn:ietf:params:scim:schemas:extension:enterprise:2.0:User). - **Create a Superblocks SCIM bulk** (Create). Submit a bulk SCIM request to Superblocks to perform multiple SCIM operations (POST, PUT, PATCH, DELETE) in a single call. Returns: schemas, Operations. Required: Operations.