mcpField
U
UseGrant MCP Server

UseGrant MCP Server

Local
github.com/usegranthqSecurity0Updated 1w ago
Repository

About UseGrant MCP Server

UseGrant MCP Server connects MCP clients to the UseGrant API for managing providers, clients, tenants, and access tokens. It generates tools from the API’s OpenAPI specification at startup, so operations reflect the spec without server updates.

Key features

  1. 01Generates tools from the OpenAPI spec
  2. 02Manages providers, clients, and tenants
  3. 03Creates and validates access tokens
  4. 04Marks read-only and destructive operations

Use cases

  1. 01List UseGrant providers
  2. 02Create clients and tenant policies
  3. 03Verify domains and validate tokens

MCP support

The MCP server exposes UseGrant API operations as tools, generated from the OpenAPI spec when it starts. It marks read-only and delete operations with hints for client-side confirmation.

#ai#oidc#mcp-server#usegrant#api-integration

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "usegranthq": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}
Run commandnpx -y @modelcontextprotocol/inspector

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@modelcontextprotocol/inspector

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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.

Requirements

  • Node.js 22.19 or higher
  • Network access to sdk.usegrant.dev, the OpenAPI spec is loaded on start
  • A 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.ts

To watch and build the project:

npm run dev

License

This project is licensed under the MIT License. See the LICENSE file for details.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.