empe-mcp-server logo

empe-mcp-server

by empe-io

The MCP Server for SSI Issuer Service acts as an adapter between AI models and the EMPE Issuer Service, enabling AI-driven credential management workflows. It allows AI assistants to interact with Issuer Service functionality through well-defined tools.

View on GitHub

Last updated: N/A

What is empe-mcp-server?

The MCP (Model Context Protocol) Server for the Empe Self-Sovereign Identity Issuer Service is a Spring Boot application that exposes Issuer Service functionality as tools that can be called by AI models. It bridges the gap between natural language interactions and SSI credential operations, allowing AI agents to create and manage verifiable credentials.

How to use empe-mcp-server?

To use the MCP server, you need to configure it with access to an EMPE Issuer Service instance. After building and running the server, you can connect AI models like OpenAI's Custom GPT or Anthropic's Claude by providing the server's API endpoint and OpenAPI schema. The AI models can then use the exposed tools to manage credential schemas and issue verifiable credentials.

Key features of empe-mcp-server

  • Exposes Issuer Service functionality as tools for AI models

  • Supports schema management (create, retrieve, delete schemas)

  • Enables credential issuance (create targeted and open offerings)

  • Built on Spring Boot and Spring AI's MCP server capabilities

  • Provides examples for integrating with OpenAI Custom GPT and Anthropic Claude

Use cases of empe-mcp-server

  • AI agents proving their identity and capabilities

  • Establishing trust between AI agents, humans, and external systems

  • Sharing verifiable information securely

  • Managing digital identities and credentials in AI agent ecosystems

FAQ from empe-mcp-server

What is Self-Sovereign Identity (SSI)?

SSI is a model for digital identity management that gives individuals (and AI agents) control over their own identities and data, without depending on a central authority.

What are the key roles in the SSI ecosystem?

The key roles are Issuers (create and sign credentials), Holders (receive and store credentials), and Verifiers (request and verify credentials).

What is the Model Context Protocol (MCP)?

MCP is a protocol that enables AI models to interact with external systems and tools, such as the EMPE Issuer Service.

How do I access the Issuer Service?

You can deploy your own instance using the one-click portal at https://oneclick.empe.io/ or use the demo environment (access code required).

What are some example AI interactions with the MCP server?

Examples include creating membership credentials, offering credentials to specific recipients, and retrieving information about supported credential types.