IssueBadge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug mode | false |
| AUTH_METHOD | No | Authentication method to use (sanctum or oauth2) | sanctum |
| MAX_RETRIES | No | Maximum number of retry attempts for failed requests | 3 |
| RETRY_DELAY | No | Delay between retry attempts in milliseconds | 1000 |
| MCP_SERVER_NAME | No | Name of the MCP server | IssueBadge MCP Server |
| REQUEST_TIMEOUT | No | Timeout for API requests in milliseconds | 30000 |
| ISSUEBADGE_API_KEY | No | Your IssueBadge API key for authentication | |
| MCP_SERVER_VERSION | No | Version of the MCP server | 1.0.0 |
| ISSUEBADGE_BASE_URL | No | The base URL for the IssueBadge API | https://app.issuebadge.com/api/v1 |
| ISSUEBADGE_OAUTH_URL | No | The OAuth URL for IssueBadge (Alternative to API key) | https://app.issuebadge.com/api/v1/oauth |
| ISSUEBADGE_OAUTH_TOKEN | No | Your OAuth token for IssueBadge authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_keyA | Validate an IssueBadge API key for authentication. Use this to test if your API credentials are working correctly. |
| get_all_badgesB | Retrieve all available badges for the authenticated organization. Returns a list of badges with their IDs and names. |
| issue_badgeA | Issue a badge to a recipient. This creates a digital certificate and sends notification email with verification URL. |
| create_badgeB | Create a new badge template with optional custom fields and branding. This badge can then be issued to recipients. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.