mcpField
I
Issuebage

Issuebage

github.com/issuebadgeOther0Updated 6d ago

About Issuebage

IssueBadge MCP server lets AI agents work with badge templates, issue certificates, and manage dynamic QR codes. It supports remote HTTP and local stdio use, with API-key authentication or OAuth for compatible hosts.

Key features

  1. 01List badge templates
  2. 02Issue certificates to recipients
  3. 03Create badges with stdio
  4. 04List and inspect QR codes
  5. 05View QR code scan data
  6. 06Delete QR codes

Use cases

  1. 01Send a completion certificate to a learner
  2. 02Check available badge templates
  3. 03Review scans of a QR code
  4. 04Create badges from a local stdio setup

MCP support

The server exposes IssueBadge badge issuance and QR code operations as tools for MCP clients. It offers a remote endpoint and a local stdio option; compatible hosts can authenticate through OAuth.

Details

From the project README

IssueBadge MCP server

Issue verifiable certificates and badges from any AI agent. This Model Context Protocol server lets Cursor, Claude, VS Code and other MCP clients list your IssueBadge badge templates and send a certificate to a recipient by name and email.

Two ways to run it:

Remote (recommended)Local (stdio)
Endpointhttps://issuebadge-mcp.issuebadge.workers.dev/mcpnpx issuebadge-mcp-server
AuthAuthorization: Bearer <API key> headerISSUEBADGE_API_KEY env var
Toolsvalidate_key, get_all_badges, issue_badge, list_qr_codes, get_qr_code, get_qr_code_scans, delete_qr_codethe same + create_badge
Storagenone, statelessnone

You need an IssueBadge API key: app.issuebadge.com → Developer → API key (https://app.issuebadge.com/developer/index).

Install

Cursor

Install IssueBadge from the Cursor Marketplace and paste your API key when prompted. Or add it by hand in Settings → MCP:

{
  "mcpServers": {
    "issuebadge": {
      "type": "streamable-http",
      "url": "https://issuebadge-mcp.issuebadge.workers.dev/mcp",
      "headers": { "Authorization": "Bearer YOUR_ISSUEBADGE_API_KEY" }
    }
  }
}
Claude Code
claude mcp add --transport http issuebadge https://issuebadge-mcp.issuebadge.workers.dev/mcp \
  --header "Authorization: Bearer YOUR_ISSUEBADGE_API_KEY"

This repo is also a Claude Code plugin (.claude-plugin/plugin.json) and ships an issuebadge skill that teaches the agent the list → confirm → issue workflow. The plugin's .mcp.json reads the key from the ISSUEBADGE_API_KEY environment variable, so export it before starting Claude Code.

Claude Desktop / any stdio client
{
  "mcpServers": {
    "issuebadge": {
      "command": "npx",
      "args": ["-y", "issuebadge-mcp-server"],
      "env": { "ISSUEBADGE_API_KEY": "YOUR_ISSUEBADGE_API_KEY" }
    }
  }
}
VS Code (Copilot agent mode)

.vscode/mcp.json:

{
  "servers": {
    "issuebadge": {
      "type": "http",
      "url": "https://issuebadge-mcp.issuebadge.workers.dev/mcp",
      "headers": { "Authorization": "Bearer YOUR_ISSUEBADGE_API_KEY" }
    }
  }
}

Tools

ToolInputReturns
validate_key–{ valid, message }
get_all_badgeslimit?{ badges: [{ id, name, description?, created_at? }] }
issue_badgebadge_id, name, email?, phone?, idempotency_key?, metadata?{ issue_id, certificate_url, idempotency_key }
create_badge (stdio only)name, description, issuing_organization_name, idempotency_key, optional badge_logo_path, custom_fields, …IssueBadge API response

issue_badge emails the certificate to the recipient and returns a public verification URL. Every call with a new idempotency_key issues a new certificate (one is generated as mcp-<uuid> if you omit it). The API rejects a reused key, so after a failed call check whether the certificate was issued before calling again with a new key.

Example prompt once installed: "Issue the Course Completion certificate to Jane Doe, [email protected]."

Dynamic QR codes
ToolInputReturns
list_qr_codestype?, limit?{ qr_codes: [...], total }
get_qr_codecodethe QR code + PNG image block
get_qr_code_scanscode, limit?{ code, scan_count, scans: [{ scanned_at, referer }], total }
delete_qr_codecode{ deleted: true, code }

Types: url, vcard, paypal, wifi, email, phone, sms, maps, event, facebook, twitter, youtube, text, mecard. Codes are created and retargeted in the IssueBadge dashboard; the image encodes an IssueBadge redirect (scan_url), so a printed code keeps working when its destination changes.

Example prompt: "Create a QR code named Menu that opens https://example.com/menu and show it to me."

ChatGPT and OAuth

The remote server also speaks OAuth 2.1 for hosts that cannot send an API key (ChatGPT apps, Claude connectors): a request without a bearer gets 401 + WWW-Authenticate: Bearer resource_metadata=…, /.well-known/oauth-protected-resource points at https://app.issuebadge.com (PKCE S256, dynamic client registration), and the issued access token is forwarded exactly like an API key. issue_badge carries a widget (ui://widget/certificate.html, MCP Apps / ChatGPT Apps SDK) that renders the certificate card. See CHATGPT.md.

Privacy and security

Self-host the remote server

git clone https://github.com/issuebadge/mcp-server && cd mcp-server
npm install
npm test
npx wrangler deploy --config worker/wrangler.toml   # needs a Cloudflare account

GET /health returns { ok: true }. Point ISSUEBADGE_BASE_URL at a different API host for the stdio server if you run IssueBadge elsewhere.

Development

npm install
npm test          # vitest: client, tools, worker (mocked IssueBadge API)
npm run build     # tsc → dist/ (stdio bin)
npm run dev:worker

Layout: src/issuebadge.ts (API client), src/tools.ts (tool registry shared by both hosts), src/stdio.ts (npm bin), src/createBadge.ts (stdio-only tool), worker/index.ts (Cloudflare Worker), .cursor-plugin/ + mcp.json (Cursor plugin), .claude-plugin/ + .mcp.json (Claude Code plugin), skills/issuebadge/SKILL.md, server.json (MCP Registry).

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.