IssueBadge MCP Server
IssueBadge MCP server lets AI agents issue verifiable certificates/badges and manage IssueBadge resources from MCP clients.
Validate an IssueBadge API key.
List available badge templates.
Issue a badge/certificate to a recipient by name, with optional email, phone, metadata, and idempotency key; returns a certificate/verification URL and emails the recipient.
Create new badge templates with custom fields and branding, in local stdio mode.
Manage dynamic QR codes: list codes, retrieve a QR code image, view scan history, and delete codes.
Run remotely over HTTP with bearer auth/OAuth or locally via npx stdio with an environment API key.
Uses .env files for configuration management, allowing customization of API credentials and server settings.
Enables integration with GitHub for issue tracking, discussions, and reporting bugs for the MCP server through GitHub Issues and GitHub Discussions.
Supports Laravel Sanctum authentication for secure API communication with the IssueBadge platform.
Built on Node.js runtime, allowing for deployment in Node.js environments with version 18+ required.
Available as an npm package for easy installation and dependency management with npm version 8+ required.
Uses TypeScript for type-safe implementation, providing better code quality and developer experience when extending or modifying the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@IssueBadge MCP Server Create a Python certification badge for completing our data science course"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
|
|
Auth |
|
|
Tools |
| the same + |
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 |
| – |
|
|
|
|
|
|
|
|
| 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 |
|
|
|
|
| the QR code + PNG image block |
|
|
|
|
|
|
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
The remote server is stateless. Your API key is read from the
Authorizationheader of each request, forwarded toapp.issuebadge.com, and never stored or logged. Requests without a key get401.The only host contacted is
app.issuebadge.com. Recipient name, email and the badge id are sent there to create the certificate.Privacy policy: https://issuebadge.com/h/policy · Terms: https://issuebadge.com/h/terms · Support: https://issuebadge.com/h/contact
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 accountGET /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:workerLayout: 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 toolscreate_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
Scored across 4 tools
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.
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.
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.
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA versatile Model Context Protocol server that enables AI assistants to manage calendars, track tasks, handle emails, search the web, and control smart home devices.23MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that allows secure execution of pre-approved commands, enabling AI assistants to safely interact with the user's system.122-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables AI assistants to manage meeting data, including creating meeting bots, searching transcripts, and organizing calendar events.30MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing AI assistants with comprehensive project, task, and subtask management capabilities with project-specific storage.2944 npm88MIT