Empeiria Documentation
  • Getting Started
    • Welcome to Empeiria
    • 5 minutes Quickstart
    • Tutorial: Credential Issuance & Verification
      • Overview
      • Understanding Key Concepts
      • Project Setup
      • Deploying the Issuer
      • Uploading the Credential Schema
      • Issuing Credentials
      • Frontend for Credential Issuance
      • Testing Credential Issuance
      • Deploying the Verifier
      • Setting Up the Verification Flow
      • Creating a Verification Endpoint
      • Creating a Protected Dashboard
      • Testing the Verification Flow
      • Summary & Next Steps
  • Understand
    • EVDI Architecture
    • Self-Sovereign Identity
      • Technical Foundations
      • Roles in the SSI framework
      • Protocols and Standards
  • Develop
    • One-click deployment
      • Introduction
      • Registration
      • Login
      • Creating an Issuer
      • Issuer Data Description
      • Creating a Verifier
      • Verifier Data Description
    • Issuer
      • Terminology and Concepts
      • DID Document Management
      • Schema Management
      • Issuing Credentials and Interacting With Wallets
      • Revocations
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • MCP Server Integration
      • FAQ
      • API Reference
        • Token
        • Schema
        • Offering
        • Metadata
        • Credential
        • Blockchain
        • Authorization
    • Verifier
      • Terminology and Concepts
      • Architecture Overview
      • Core Responsibilities
      • Query Language
      • Client Configuration
      • Frontend Integration
      • Revocations
      • Server-Side VP Queries
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • MCP Server Integration
      • FAQ
      • API Reference
        • VP Query
        • QR Code
        • Authorization
    • Wallet SDK (Coming soon)
    • Introduction to cosmwasm
  • Empe Blockchain
    • Overview
    • Chain Architecture
      • Auth
      • Authz
      • Bank
      • Distribution
      • Governance
      • Staking
      • IBC
      • DidDoc
      • Vesting
      • Minter
      • Stablefee
      • LinkedResources
    • Important links
    • Validators Guide
      • New validator
      • Hardware requirements
      • Required software installation
      • Go installation
      • Install prebuild binary
      • Install binary from source code (option B)
      • Configure a node
      • Cosmovisor setup
      • Install wasmvm
      • Sync with state-sync
      • Full state sync from archive snapshot
      • Latest snapshot
      • Run a Validator
      • Migration to v0.2.2
      • Migration to v0.3.0
      • Migration to v0.4.0
      • FAQ
  • User Guide
    • Empe DID Wallet
      • Intro
      • Download and first launch
      • Create or import did
      • Main screen overview
      • How to claim credential from issuer
      • How to use credential with verifier
      • Settings and other options
    • Keplr Wallet and Blockchain Operations
      • How to Connect Keplr Wallet
    • Ping Pub operation
    • Staking Tokens Guide
    • Voting on Governance Proposals Guide
    • Sending Tokens Guide
    • Airdrop
      • On-Chain Testnet Airdrop
      • Faucet Guide: How to Claim Testnet Tokens?
  • Appendix
    • Glossary
Powered by GitBook
On this page
  • What is MCP?
  • Available Issuer Operations
  • Schema Management
  • Credential Issuance
  • Example Use Cases
  • Setup Requirements
  • Integration Benefits
  • Configuration
  • Security Considerations
  1. Develop
  2. Issuer

MCP Server Integration

The Empe MCP Server enables AI systems like Claude to interact with the Issuer Service through natural language commands. This Model Context Protocol (MCP) server provides a bridge between conversational AI and SSI operations, making credential issuance and schemas management accessible through simple prompts.

What is MCP?

MCP (Model Context Protocol) servers provide context, tools, and prompts to AI clients. They expose data sources like files, databases, and APIs to make them accessible to AI systems. The Empe MCP server allows you to control the Issuer Service through natural language prompts.

Available Issuer Operations

The MCP server provides these issuer-related tools:

Schema Management

  • create_schema - Create new credential schemas through natural language

  • get_all_schemas - List all available schemas in the system

  • get_schema_by_id - Retrieve specific schema details

  • delete_schema - Remove unused schemas

  • schema_exists_by_type - Check if a schema type already exists

  • get_latest_schema_by_type - Get the most recent version of a schema

Credential Issuance

  • create_offering - Generate credential offerings with QR codes

  • show_qr_code - Display QR codes for credential claiming

Example Use Cases

You can use natural language prompts like:

"Create a digital ticket schema for my tech conference with fields for 
event name, date, seat number, and ticket ID."

"Issue a membership card for John Doe with Gold level membership 
expiring on December 31, 2024."

"Show me all the credential schemas available in the system."

"Generate a QR code for claiming a concert ticket for the Summer Jazz Festival."

Setup Requirements

Before using the MCP server with the Issuer Service:

  1. Deploy an Issuer Service via One-Click Deployment

  2. Configure the MCP server with your issuer's API endpoint and credentials

  3. Connect the MCP server to your AI client (like Claude)

Integration Benefits

  • Rapid Prototyping: Create and test credential schemas instantly through conversation

  • Non-Technical Access: Enable non-developers to work with SSI systems

  • Workflow Automation: Chain multiple operations through natural language

  • Educational Tool: Learn SSI concepts through interactive exploration

Configuration

The MCP server requires these issuer-related environment variables:

ISSUER_URL=https://your-issuer-instance.example.com
ISSUER_API_KEY=your-issuer-api-key

For detailed setup instructions, see the MCP Server repository.

Security Considerations

When using the MCP server with production issuer services:

  • Use dedicated test environments for experimentation

  • Implement proper access controls for the MCP server

  • Monitor AI-generated schema and credential operations

  • Validate all AI-created schemas before production use

The MCP server makes SSI development more accessible while maintaining the security and standards compliance of the underlying Issuer Service.

PreviousReferences and StandardsNextFAQ

Last updated 2 days ago