Application Development
Superblocks
Connect Superblocks once and hand every teammate a governed MCP endpoint with 16 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
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 ship on the Black plan.
Automations
Put Superblocks work on a schedule.
A trigger starts a sequence of steps: call a Superblocks tool, transform the result, branch, wait, and ask a person when it matters.
Superblocks digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch scim users
Superblocks
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Superblocks
Queued
Collections and dashboards
Report on Superblocks without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Superblocks health
Refreshed 4 minutes ago · every 15 minutes · from the scim users collection
Scim users
1,284 ↓ 12%
Scim groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Scim users created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
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.
list_all_superblocks_scim_users
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 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 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 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
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
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 Superblocks SCIM groups. Returns: schemas, id, displayName, members, meta.
create_a_superblocks_scim_group
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 a single Superblocks SCIM group by id. Returns: schemas, id, displayName, members, meta. Required: id.
update_a_superblocks_scim_group_by_id
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 a Superblocks SCIM group by id. Returns an empty 204 response on success. Required: id.
superblocks_scim_groups_partial_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
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 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 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
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.
No tools match your search.
How it works
From Superblocks account to governed MCP endpoint
Connect
Link a Superblocks account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Superblocks tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.