useblip/email
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLIP_API_KEY | Yes | Your Blip API key. Create one at https://useblip.email/app |
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 |
|---|---|
| create_inboxB | Create a new disposable email inbox. Returns the inbox ID and email address. |
| list_inboxesA | List all active inboxes for the current API key. |
| get_inboxA | Get inbox details and list of received emails. |
| read_emailB | Read the full content of a specific email including body, headers, and attachments. |
| extract_codesA | Extract OTP codes and verification links from the most recent email in an inbox. Use this after creating an inbox and receiving a verification/signup email. |
| wait_for_emailA | Poll an inbox until an email arrives. Returns the email once received. Times out after the specified duration. |
| delete_inboxA | Delete an inbox and all its emails. |
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 7 tools
Each tool targets a distinct operation: inbox lifecycle (create, delete, list, get), email reading, waiting, and code extraction. No overlap in purpose; an agent can clearly distinguish which tool to use for a given task.
All tool names follow a consistent snake_case verb_noun pattern (e.g., create_inbox, list_inboxes, read_email, extract_codes). The naming is uniform and predictable, making it easy to understand the action and resource.
With 7 tools, the set is well-scoped for a disposable email server. Each tool provides a necessary part of the workflow (creation, management, retrieval, extraction) without bloat or excessive specialization.
The tool surface covers the full lifecycle of a disposable inbox: creation, listing, reading, waiting for emails, extracting codes, and deletion. No obvious gaps exist for the intended use case, as sending emails is not part of a disposable inbox service.