UseGrant MCP Server
OfficialThe UseGrant MCP Server is a comprehensive tool for managing the UseGrant API resources, including:
Providers: List, create, get, and delete providers
Clients: List, create, get, and delete clients for providers
Domains: List, add, get, delete, and verify domains for providers
Access Tokens: Create tokens for clients and validate tokens for tenants
Tenants: List, create, get, and delete tenants
Tenant Providers: List, create, get, and delete providers associated with tenants
Tenant Provider Policies: List, create, get, and delete policies for tenant providers
Supports environment variable management for the UseGrant MCP server, particularly for storing and accessing the USEGRANT_API_KEY.
Supports the execution of the UseGrant MCP server, which requires Node.js 16 or higher to run the server and interact with the UseGrant API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@UseGrant MCP Server list all providers for tenant tnt_123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
UseGrant MCP Server
This is a Model Context Protocol (MCP) server for interacting with the UseGrant API. It provides a set of tools for managing providers, clients, tenants, and access tokens through the UseGrant platform.
Tools
The tools are generated from the UseGrant OpenAPI spec when the server starts, one tool per API operation, so new API operations are available without updating the server.
Tools are named after the operation, for example:
providers_list: List Providers
providers_clients_create: Create Client
providers_domains_verify: Verify Domain
tenants_providers_policies_create: Create Tenant Provider Policy
tenants_tokens_validate: Validate Token
Read-only operations are marked with readOnlyHint and delete operations with destructiveHint, so MCP clients can ask for confirmation before changing anything.
Related MCP server: MCP Boilerplate
Requirements
Node.js 22.19 or higher
Network access to
sdk.usegrant.dev, the OpenAPI spec is loaded on startA valid UseGrant API key. Refer here for more details.
Using with Claude desktop
Add the following config to your claude_desktop_config file:
{
"mcpServers": {
"usegrant": {
"command": "npx",
"args": ["-y", "@usegrant/mcp"],
"env": {
"USEGRANT_API_KEY": "your_api_key_here"
}
}
}
}Testing
To test the MCP server, we can use mcp inspector.
Copy the .env.example file to .env and set the USEGRANT_API_KEY environment variable.
npx @modelcontextprotocol/inspector -e USEGRANT_API_KEY=$USEGRANT_API_KEY npx tsx src/index.tsTo watch and build the project:
npm run devLicense
This project is licensed under the MIT License. See the LICENSE file for details.
Available Tools
27 toolsproviders_clients_createCreate ClientD
Create Client
Inputs: name (required), audience (required), providerId (required).
providers_clients_deleteDelete ClientCDestructiveIdempotent
Delete Client
Inputs: clientId (required), providerId (required).
providers_clients_getGet ClientCRead-onlyIdempotent
Get Client
Inputs: clientId (required), providerId (required).
providers_clients_listList ClientsCRead-onlyIdempotent
List Clients
Inputs: providerId (required).
providers_clients_tokens_createCreate Access TokenD
Create Access Token
Inputs: clientId (required), providerId (required), expiresIn, useJwtType, +2 more.
providers_createCreate ProviderD
Create Provider
Inputs: name (required), description (required).
providers_deleteDelete ProviderCDestructiveIdempotent
Delete Provider
Inputs: id (required).
providers_domains_addAdd Domain to ProviderC
Add Domain to Provider
Inputs: domain (required), providerId (required).
providers_domains_deleteDelete DomainCDestructiveIdempotent
Delete Domain
Inputs: domainId (required), providerId (required).
providers_domains_getGet DomainDRead-onlyIdempotent
Get Domain
Inputs: domainId (required), providerId (required).
providers_domains_listList DomainsCRead-onlyIdempotent
List Domains
Inputs: providerId (required).
providers_domains_verifyVerify DomainC
Verify Domain
Inputs: domainId (required), providerId (required).
providers_getGet ProviderCRead-onlyIdempotent
Get Provider
Inputs: id (required).
providers_listList ProvidersCRead-onlyIdempotent
List Providers
Inputs: no named parameters.
tenants_createCreate TenantD
Create Tenant
Inputs: name (required), description (required).
tenants_deleteDelete TenantDDestructiveIdempotent
Delete Tenant
Inputs: id (required).
tenants_getGet TenantCRead-onlyIdempotent
Get Tenant
Inputs: id (required).
tenants_listList TenantsCRead-onlyIdempotent
List Tenants
Inputs: no named parameters.
tenants_providers_createCreate Tenant ProviderD
Create Tenant Provider
Inputs: url (required), audience (required), tenantId (required), fingerprints (required), +1 more.
tenants_providers_deleteDelete Tenant ProviderCDestructiveIdempotent
Delete Tenant Provider
Inputs: tenantId (required), tenantProviderId (required).
tenants_providers_getGet Tenant ProviderCRead-onlyIdempotent
Get Tenant Provider
Inputs: tenantId (required), tenantProviderId (required).
tenants_providers_listList Tenant ProvidersCRead-onlyIdempotent
List Tenant Providers
Inputs: tenantId (required).
tenants_providers_policies_createCreate Tenant Provider PolicyD
Create Tenant Provider Policy
Inputs: name (required), audience (required), tenantId (required), description (required), +2 more.
tenants_providers_policies_deleteDelete Tenant Provider PolicyCDestructiveIdempotent
Delete Tenant Provider Policy
Inputs: policyId (required), tenantId (required), tenantProviderId (required).
tenants_providers_policies_getGet Tenant Provider PolicyCRead-onlyIdempotent
Get Tenant Provider Policy
Inputs: policyId (required), tenantId (required), tenantProviderId (required).
tenants_providers_policies_listList Tenant Provider PoliciesCRead-onlyIdempotent
List Tenant Provider Policies
Inputs: tenantId (required), tenantProviderId (required).
tenants_tokens_validateValidate TokenD
Validate Token
Inputs: token (required), tenantId (required), tenantProviderPolicyId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 27 tools
The hierarchical resource paths make most tools clearly distinct, especially across providers, clients, domains, tenants, tenant providers, and policies. Some boundaries are still easy to confuse, such as provider clients' token creation versus tenant token validation, but descriptions provide enough context.
Tool names consistently use snake_case with a hierarchical resource path followed by a verb, such as providers_clients_list and tenants_providers_policies_create. Domain-specific verbs like add and verify are used appropriately without breaking the overall pattern.
The 27-tool surface is heavy for a single MCP server, but it is structured around CRUD operations for several nested resource types rather than arbitrary one-off tools. It is borderline appropriate for a multi-tenant provider/client/domain/policy domain, though still larger than ideal.
The server covers many core list/get/create/delete operations across providers, clients, domains, tenants, tenant providers, and policies. However, update operations are largely absent, and token lifecycle coverage is incomplete because there is token creation and validation but no token listing, revocation, or deletion.
Maintenance
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
The Stytch MCP server is a reference implementation that demonstrates remote MCP server authentication and authorization using Stytch Connected Apps. It provides OAuth 2.1-compliant authorization (including PKCE), Dynamic Client Registration, and validates Stytch-issued access tokens to enable AI agents to securely interact with external services through permissioned access, supporting scopes like openid, email, profile, and manage:project_data.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseBqualityBmaintenanceA Model Context Protocol server that provides tools to manage Keycloak users and realms, allowing you to create and delete users, list available realms, and view users in specific realms.4185 npm47MIT
- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.12MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that supports remote connections and authenticates users via GitHub OAuth, allowing them to access tools based on their GitHub identity.-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables management of Keycloak users and realms through a standardized interface, providing tools for user creation, deletion, role assignment, and group management.9108 npm13MIT