postcardbot-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTCARDBOT_API_KEY | Yes | Your API key from postcard.bot/account | |
| POSTCARDBOT_API_URL | No | Override API base URL (default: https://postcard.bot) | https://postcard.bot |
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 |
|---|---|
| send_postcardA | Send a physical postcard that will be printed and mailed to a real address. Price depends on volume tier based on lifetime top-up (from $0.72–$1.99 USA, $1.99–$2.99 international). Charged from the user's prepaid Postcard.bot balance. Use check_balance to see current pricing tier before sending. Requires an image URL (publicly accessible) and a message (max 350 characters). |
| check_balanceA | Check account balance, lifetime top-up amount, and current volume pricing tier. Use this before sending to know your per-postcard cost and available funds. |
| get_pricingB | Get postcard pricing tiers based on lifetime top-up amount. USA from $1.99 (<$50) down to $0.72 ($5000+), International from $2.99 down to $1.99. |
| bulk_sendA | Send the same postcard to multiple recipients at once. Same message, image, and return address for all cards — only the recipient addresses differ. Maximum 500 recipients per request. Total cost is deducted upfront from balance; failed cards are automatically refunded. Volume pricing applies based on your tier. |
| check_statusA | Check the delivery status of a previously sent postcard. Returns the current status, delivery tracking info, and expected delivery date. |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: bulk_send handles mass mailing, send_postcard for single cards, check_balance for account info, check_status for tracking, and get_pricing for cost details. The descriptions reinforce these boundaries, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., bulk_send, check_balance, send_postcard). This uniformity makes the set predictable and easy for agents to understand and navigate.
With 5 tools, this server is well-scoped for its postcard-sending domain. Each tool serves a specific, essential function (sending, checking, pricing, status) without redundancy, making the count appropriate and manageable.
The tool surface provides complete coverage for the postcard-sending workflow: send_postcard and bulk_send for creation, check_status for tracking, check_balance for account management, and get_pricing for cost planning. There are no obvious gaps that would hinder agent operations.