Schema | capline-mcp

capline-mcp

Official

Describes the environment variables required to run the server.

Name	Required	Description	Default
`CAPLINE_COORDINATOR_URL`	No	The URL of the Capline coordinator	https://capline-protocol.vercel.app/api/coordinator

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
create_mandateA	Provision a spend mandate the agent must operate under: a per-transaction cap, a cumulative cap enforced GLOBALLY across every chain, and an optional payee allowlist. Returns a mandateId to pass to `pay`. Normally the human principal sets this up once, before handing the agent any spending ability.
payA	Make a payment on behalf of the agent. THIS IS THE ONLY WAY TO MOVE FUNDS, and it is enforced by the mandate: the payment is REFUSED (not executed) if it exceeds the per-transaction cap, the payee is not on the allowlist, or it would breach the global cross-chain cap. A prompt injection in the agent's context cannot bypass this.
mandate_statusA	Read a mandate's current state: committed spend, reserved, remaining budget, and the per-chain breakdown.
revoke_mandateA	Revoke a mandate. After this, every payment under it is refused on every chain.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/caplinehq/capline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server