thatsme MCP Issuer
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for HTTP transport (only if MCP_TRANSPORT=http) | 3010 |
| MCP_TRANSPORT | No | Transport mode (stdio or http) | stdio |
| THATSME_API_KEY | Yes | Your thatsme API key (required) | |
| THATSME_API_URL | No | API base URL override | https://service.thatsme.com.br/api |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_eventsA | Search events created by your organization in thatsme. Use to find a specific event before issuing certificates or checking engagement. Returns event_id, name, date, and total emissions count. |
| issue_certificatesA | Issue digital certificates to a list of recipients for a specific event. Each recipient receives a 3D badge via email (and WhatsApp if enabled). Requires PRO plan or higher. Returns emission_id and status per recipient. |
| get_engagement_funnelA | Get the engagement funnel for a specific event: how many certificates were issued, accepted, viewed, shared on LinkedIn, and clicked on recommendations. Use to understand event performance. Requires PRO plan or higher. |
| list_recipientsA | List recipients for a specific event with their certificate status (pending, accepted, refused). Paginated, max 50 per page. Emails are partially masked for privacy. Requires PRO plan or higher. |
| export_csvA | Export emission data for all events as a CSV file. Returns the CSV content as a string. Each row is one event with: name, total issued, accepted, acceptance rate, last emission date. Requires PRO plan or higher. |
| validate_retroactive_achievementA | Issue an official retroactive certificate (Post) from a user-submitted unverified Achievement. The caller MUST be an admin of the Company that owns the provided event_id and badge_id — thatsme rejects cross-issuer attempts. The original conquest date is preserved on the certificate. Used for the Hugo Furtado lead-conversion flow. |
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 6 tools
Each tool serves a distinct purpose: searching events, issuing certificates, viewing engagement funnels, listing recipients, exporting CSV, and validating retroactive achievements. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (search_events, issue_certificates, get_engagement_funnel, etc.). The naming is predictable and easy to understand.
With 6 tools, the server is well-scoped for its purpose of certificate issuance and event tracking. Each tool earns its place and there are no redundant utilities.
The tool set covers the core lifecycle of searching events, issuing certificates, and analyzing engagement. Minor gaps exist such as the lack of update/delete operations for events or certificates, but these are not essential for the server's focus.