MCP/AI Integration

The Wallet Server's holder API is a good fit for AI agents that need to act as a credential holder. Every operation is a plain, synchronous HTTP call, so it can be exposed as tools in a Model Context Protocol (MCP) server or any other agent framework:

• Create a holder wallet — POST /agent/holder (choose did:key or did:web)

• Process a URI — POST /holders/:holderId/process claims a credential offer or answers a presentation request from QR-code content

• List stored credentials — GET /holders/:holderId/credentials and GET /holders/:holderId/credentials/decoded

Typical Agent Tasks

• "Create a holder wallet and tell me its DID."

• "Process this credential-offer URI and confirm the credential was stored."

• "Scan the verifier QR and present the matching credential."

Setup Notes for Agents

• Authenticate with Authorization: Bearer <JWT>; the token's sub identifies the agent/user and scopes holder ownership

• Keep tokens short-lived; refresh as needed

• Point agents to Swagger UI at /api-docs or the OpenAPI JSON at /api-docs-json to discover operations

Local Development

For local development set AUTH_DISABLED=true; every request is then treated as an authenticated admin, so no token is needed. Never enable this outside local development.