# grantor-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://chaingrantor.com/docs/guide/mcp-broker.html  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/grantor-mcp

## Description
Bounded, revocable authority for sub-agents — grant, narrow, check, revoke. No auth server.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What grantor-mcp does

grantor-mcp MCP server provides a control point for delegated authority used by sub-agents. Its stated scope is deliberately narrow: authority can be granted, reduced, inspected, or withdrawn. This makes it relevant to agent workflows in which one component needs to give another component limited permission and retain the ability to change or remove that permission.

The material identifies four core actions:

- Grant authority to a sub-agent.
- Narrow previously granted authority.
- Check the current authority state.
- Revoke authority.

These actions describe authority management, not user authentication. The project description explicitly says that it is not an authentication server, so it should not be selected as a replacement for a service that authenticates users, agents, or applications.

## How it works

The grantor-mcp MCP server is centered on a grant lifecycle. A workflow starts by granting authority, can reduce the delegated scope with a narrowing operation, can inspect the current state with a check operation, and can terminate the delegation through revocation. The available material does not define the authority data model, required arguments, response format, persistence behavior, or enforcement mechanism.

This model is useful when delegation must remain bounded and reversible. For example, a parent agent could use the stated operations to manage the authority assigned to a sub-agent over the course of a task. The source material does not specify which resources or actions can be covered by a grant, so those details should be confirmed in the project documentation before implementation.

## Tools and capabilities

The documented capabilities are the following:

- **Grant:** create or assign delegated authority.
- **Narrow:** reduce the authority available to a sub-agent.
- **Check:** inspect authority status.
- **Revoke:** withdraw delegated authority.

The available description does not provide formal tool names, parameters, return values, examples, or error behavior. Treat these labels as the documented capability areas rather than as a complete API reference.

## Setup and configuration

No setup instructions are available in the supplied material. It does not identify a package, launch command, transport, configuration file, required environment variables, or supported MCP clients. As a result, installation and runtime configuration cannot be stated reliably here. Consult the linked project documentation for those details before configuring grantor-mcp MCP server in an agent host.

## Limitations and notes

The clearest boundary is that grantor-mcp MCP server does not provide an authentication server. Its documented purpose is bounded, revocable authority for sub-agents. The source does not establish whether it authenticates callers, stores grants, enforces permissions against external systems, or integrates with a particular identity provider.

It also does not name supported editors, desktop applications, command-line clients, programming languages, or deployment environments. Client compatibility therefore cannot be inferred from the description alone. Developers evaluating it should verify the transport and host requirements, then confirm how grant, narrow, check, and revoke map to their own delegation model.

_Full upstream README: https://allmcps.com/mcp/grantor-mcp/readme_