Skip to main content
Glama

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)

Endpoint

https://issuebadge-mcp.issuebadge.workers.dev/mcp

npx issuebadge-mcp-server

Auth

Authorization: Bearer <API key> header

ISSUEBADGE_API_KEY env var

Tools

validate_key, get_all_badges, issue_badge, list_qr_codes, get_qr_code, get_qr_code_scans, delete_qr_code

the same + create_badge

Storage

none, stateless

none

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" }
    }
  }
}

Related MCP server: Command Executor MCP Server

Tools

Tool

Input

Returns

validate_key

–

{ valid, message }

get_all_badges

limit?

{ badges: [{ id, name, description?, created_at? }] }

issue_badge

badge_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, jane@example.com."

Dynamic QR codes

Tool

Input

Returns

list_qr_codes

type?, limit?

{ qr_codes: [...], total }

get_qr_code

code

the QR code + PNG image block

get_qr_code_scans

code, limit?

{ code, scan_count, scans: [{ scanned_at, referer }], total }

delete_qr_code

code

{ 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

Available Tools

4 tools
create_badgeB

Create a new badge template with optional custom fields and branding. This badge can then be issued to recipients.

Inputs: name (required), description (required), issuing_organization_name (required), idempotency_key (required), +7 more.

get_all_badgesB

Retrieve all available badges for the authenticated organization. Returns a list of badges with their IDs and names.

Inputs: limit.

issue_badgeA

Issue a badge to a recipient. This creates a digital certificate and sends notification email with verification URL.

Inputs: badge_id (required), name (required), idempotency_key (required), email, +2 more.

validate_keyA

Validate an IssueBadge API key for authentication. Use this to test if your API credentials are working correctly.

Inputs: api_key (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create_badge (template creation), get_all_badges (list retrieval), issue_badge (awarding to recipients), and validate_key (authentication testing). There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (create_badge, get_all_badges, issue_badge, validate_key), using snake_case throughout. This predictability enhances usability and reduces cognitive load for agents.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of managing digital badges. Each tool serves a distinct and essential function (create, list, issue, authenticate), with no unnecessary or redundant tools, making the count appropriate.

    Completeness4/5

    The tool set covers core CRUD operations for badges (create and list) and key actions (issue and validate), but lacks update and delete capabilities for badges. This minor gap might require workarounds but does not severely hinder basic workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers