Fullmakt

What Fullmakt MCP server does

The Fullmakt MCP server is described as a credential broker for AI agents. It sits between an agent and API access, providing a way to issue permissions with defined scope instead of handing the agent unrestricted credentials. Access can also be revoked, which supports removing permissions after a task, workflow, or incident.

The service is intended for environments where agent access needs explicit controls. Its stated responsibilities are credential brokering, scope management, revocation, policy enforcement, and auditing. The available description does not name the external APIs or services that can be accessed through it.

How it works

Fullmakt represents API access as permissions that can be limited in scope. Policies govern how those permissions may be used, while revocation provides a way to invalidate access later. Audit capabilities record information about access activity, giving operators a way to review how credentials were used.

The Fullmakt MCP server therefore addresses the control layer around agent API access. It is relevant when an AI agent must call external APIs but the surrounding system requires constrained permissions, the ability to withdraw access, and an audit trail. The supplied material does not explain the policy language, credential storage model, approval flow, or audit format.

Tools and capabilities

The documented capabilities include:

• Brokering credentials for AI agents
• Granting scoped API access
• Revoking API access
• Enforcing access policies
• Auditing credential or API activity

These capabilities describe the server’s role, but they do not establish a specific list of MCP tool names or parameters. Developers should verify the available tool schema and supported API targets before adopting the Fullmakt MCP server for a particular integration.

Limitations and notes

The available source is a short product description rather than a README or technical reference. It does not provide installation commands, configuration fields, environment variables, authentication steps, transport details, supported MCP clients, supported third-party APIs, or licensing information. Those details cannot be inferred from the description alone.

Fullmakt is best evaluated as an access-control component for agent-connected APIs. Whether it fits a deployment depends on the policies it can express, the credential types it supports, the APIs it can broker, and the audit data it exposes. Confirm those implementation details in the project’s technical documentation before configuring it in production.