pingen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINGEN_API_BASE | No | API base URL, defaults to https://api.pingen.com | https://api.pingen.com |
| PINGEN_ORG_UUID | No | Organisation UUID (auto-detected if not provided) | |
| PINGEN_CLIENT_ID | Yes | OAuth2 client ID from Pingen dashboard | |
| PINGEN_CLIENT_SECRET | Yes | OAuth2 client secret from Pingen dashboard |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingen_statusA | Verify credentials and show the active Pingen organisation (name, plan, id). |
| pingen_list_lettersB | List letters with status and tracking. Optional page size. |
| pingen_send_letterA | Upload a PDF and create a letter. By default a DRAFT (auto_send=false) — nothing is mailed until pingen_submit_letter. Set auto_send=true to mail immediately; that path also requires delivery_product, because it is the one route that never reaches pingen_submit_letter and so nothing asks for a product later. |
| pingen_submit_letterA | IRREVERSIBLE AND CHARGEABLE: prints and physically mails an existing DRAFT letter. Requires confirm:true. Optional print_mode (simplex/duplex) and print_spectrum (color/grayscale). |
| pingen_get_letterB | Get one letter status/tracking by id. |
| pingen_cancel_letterB | Cancel a letter that has already been submitted/sent (where cancellable). |
| pingen_delete_letterA | DESTRUCTIVE: delete a draft / not-yet-sent letter for good. Requires confirm:true. To stop a letter already on its way use pingen_cancel_letter instead. |
| pingen_letter_eventsB | Tracking/status history of a letter (created, submitted, sent, delivered, undeliverable …). |
| pingen_download_letterA | Download the letter PDF to output_path (available once the letter is processed/sent). |
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 9 tools
Most tools target distinct operations: send, submit, get, list, download, cancel, delete, events, and status. pingen_get_letter and pingen_letter_events both relate to tracking, but the former gives current status while the latter gives history, so they are distinguishable with the provided descriptions.
All tools share the 'pingen_' prefix and most follow verb_noun naming (e.g., pingen_send_letter, pingen_delete_letter). pingen_letter_events and pingen_status deviate from the verb pattern, but the overall convention is predictable and clear.
Nine tools cover the full letter lifecycle—creating, submitting, tracking, downloading, cancelling, deleting—plus an org status check. The count is well-scoped and each tool serves a clear purpose without unnecessary bloat.
The tool set covers the complete workflow for sending physical letters: upload/create, submit, monitor events/status, download PDF, cancel sent letters, and delete drafts. No obvious gaps in the core domain of letter management.