Connect an AI assistant (MCP)

Hero ID exposes a Model Context Protocol (MCP) endpoint so you can ask an AI assistant about your store’s verification data in plain language — for example, “Is this customer verified?” or “What are my current discount settings?”

Access is read-only and scoped to your store: a token only ever sees your own shop’s data.

1. Generate a token

In the Hero ID app, go to Settings → MCP access and click Generate token. Copy the token immediately — it’s shown only once. (You can rotate or revoke it on the same screen at any time.)

2. Connect your AI client

Add Hero ID as an HTTP MCP server in your client (for example, Claude Desktop):

• URL: https://hero-id.com/mcp
• Authorization header: Bearer <your token>

In Claude Desktop, for instance, this goes in your MCP servers configuration as a streamable-HTTP server with the Authorization header set to your token.

3. Ask away

Once connected, the assistant can use these tools:

Tool	What it does
get_customer_verification_status	Look up a customer’s most recent claim by email — approved, pending, needs review, or rejected.
get_discount_settings	Your current discount type, value, eligible groups, collection scope, and whether it’s active.
list_claims	Recent verification claims, newest first, optionally filtered by status.
get_verification_stats	Counts of claims by status.

Example prompts:

• “Is jane@example.com verified in Hero ID?”
• “What discount do verified customers get, and which groups qualify?”
• “List my claims that still need review.”
• “How many approved verifications do I have?”

Security

• The token grants read-only access — it can’t change discounts, approve or reject claims, or modify anything.
• Each token is scoped to the store that created it. It can’t read any other merchant’s data.
• The token is shown once at creation and stored only as a hash. If it leaks, revoke it in Settings → MCP access and generate a new one.
• For status definitions (pending vs needs review, etc.), see How verification works.