Application Development · Beta
Superblocks
API integration
Ship Application Development features without building the integration. Full Superblocks API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Superblocks
Common scenarios for SaaS companies building Superblocks integrations for their customers.
Automate identity lifecycle for Superblocks users
HRIS and SaaS management platforms can auto-provision, update, and deprovision Superblocks accounts as employees join, change roles, or leave — eliminating manual IT work and closing security gaps for internal tools.
Continuous access reviews for compliance
Compliance and GRC platforms can pull Superblocks users, groups, and memberships to generate SOC2/ISO user access reviews, proving that only authorized engineers hold Builder or Admin roles on sensitive internal tools.
Zero-touch access request fulfillment
ITSM and access management tools can resolve ticket-based access requests by programmatically adding or removing users from Superblocks SCIM groups the moment a manager approves — no manual IT intervention required.
License optimization and dormant account cleanup
SaaS spend management tools can detect inactive Superblocks accounts and use SCIM updates to downgrade or deactivate seats, reducing license costs and shrinking the attack surface for enterprise customers.
Bulk IdP-to-Superblocks migration
Identity platforms and migration tools can synchronize hundreds of users and groups from a central directory into Superblocks in a single bulk SCIM operation, making enterprise rollouts fast and consistent.
What You Can Build
Ship these features with Truto + Superblocks
Concrete product features your team can ship faster by leveraging Truto’s Superblocks integration instead of building from scratch.
Automated user provisioning and deprovisioning
Create, update, and delete Superblocks users directly from your product whenever a customer's employee is onboarded or offboarded in an upstream system.
Group-based role assignment engine
Add and remove users from Superblocks SCIM groups via PATCH operations to dynamically grant or revoke access to specific internal apps and data connections.
User access review dashboards
Surface a live view of every Superblocks user, their active status, and group memberships so customers can attest to access during audits.
Bulk sync for enterprise onboarding
Ship a one-click migration flow that pushes users and group assignments into Superblocks in a single bulk SCIM call, ideal for large-tenant rollouts.
Dormant account detection and remediation
Combine your usage signals with partial user updates to automatically deactivate or downgrade Superblocks accounts that haven't been used recently.
Directory-to-Superblocks group mirroring
Keep security groups in your product perfectly mirrored to Superblocks groups, so entitlement changes flow through automatically without IT tickets.
SuperAI
Superblocks AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
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.
Why Truto
Why use Truto’s MCP server for Superblocks
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 650+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Go live with Superblocks in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Superblocks account
Use Truto’s frontend SDK to connect your customer’s Superblocks account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Superblocks
Truto’s Proxy API is a 1-to-1 mapping of the Superblocks API. You call us, we call Superblocks, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Superblocks’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Superblocks on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
What Superblocks API does this integration use?
Truto integrates with Superblocks' SCIM 2.0 API, which covers Users, Groups, Service Provider Config, Resource Types, Schemas, and Bulk operations. Application building, database connections, and end-user runtime data are not exposed through this API.
How does authentication work for end users?
Superblocks SCIM uses a bearer token issued from the customer's Superblocks organization. Your end users provide this token during the connection flow in your product, and Truto securely stores and manages it for all subsequent API calls.
Which SCIM operations are supported?
You can list, create, read, fully update (PUT), partially update (PATCH), and delete both users and groups. Bulk operations are also supported for submitting multiple SCIM changes in a single request.
Can I sync group memberships and role assignments?
Yes. Group membership changes are performed via PATCH on the group resource, letting you add or remove users from Superblocks groups that map to roles like Admin, Builder, or Viewer.
Is bulk provisioning supported for large migrations?
Yes. The SCIM Bulk endpoint accepts multiple POST, PUT, PATCH, and DELETE operations in a single call, which is the recommended approach for onboarding or migrating hundreds of users at once.
How do I know which attributes and schemas Superblocks supports?
The integration exposes SCIM Service Provider Config, Resource Types, and Schemas endpoints, so you can programmatically discover which user and group attributes a given Superblocks tenant supports before writing to them.
From the Blog
Superblocks integration guides
Deep dives, architecture guides, and practical tutorials for building Superblocks integrations.
Superblocks
Get Superblocks integrated into your app
Our team understands what it takes to make a Superblocks integration successful. A short, crisp 30 minute call with folks who understand the problem.