Grafbase
Grafbase is a platform that accelerates the development of GraphQL APIs, offering features like edge caching, unified data access, and seamless integration with popular authentication strategies.
In development
Cataloged and scoped, not yet available to run in production.
- 28
- actions
Integrations
View provider documentationActions
Operations this integration can perform.
Add Zitadel Redirect URI
Add a redirect URI to Zitadel OAuth configuration in Grafbase. Use when you need to register a new redirect URI for OAuth flows with Zitadel identity provider.
Assign Team Role
Tool to assign a role to a team member in Grafbase. Use this when you need to change a team member's role between MEMBER and ADMIN. ADMIN role grants team management privileges including adding/removing members and changing roles.
Delete Grafbase API Key
Tool to delete an existing API key. Use after confirming the key ID to revoke access.
Delete Grafbase Audit Log
Tool to delete a specific Grafbase audit log entry. Note: As of current Grafbase public documentation, there is no documented API to delete audit logs programmatically. This action will attempt a best-effort REST DELETE to `/audit-logs/{id}` and, if unsupported or not found, it will gracefully fall back to validating connectivity with the GraphQL Management API and return a structured response instead of failing.
Delete Extension
Tool to delete an extension configuration. Use after confirming the extension_id to remove the extension.
Delete MCP Server
Tool to delete a Grafbase MCP server configuration by its unique ID. Use after confirming the server ID to remove an existing MCP server.
Delete Grafbase Schema
Tool to delete a Grafbase schema. Use when you need to remove a specific schema from the registry after confirming its ID.
Delete Schema Check
Tool to delete a Grafbase schema check. Use when you need to remove a specific schema check by its ID after reviewing the registry.
Triggers
Events that start workflows from this integration.
Custom Schema Check Run
Fires every time schema checks are run for a subgraph, allowing for custom validation.
Gateway On Request
Fires immediately after the Grafbase Gateway receives a request, before processing it.
Gateway On Response
Fires immediately before the Grafbase Gateway sends the response back to the client.
Related integrations
Don't see the exact action you need?
Tell us what you're trying to connect and we'll help you evaluate whether it fits the current catalog or needs prioritizing.