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 resource/action: create/delete/get/list operate on inboxes, while read_email, extract_codes, and wait_for_email operate at the email level with clearly differentiated purposes. Descriptions make the granularity boundaries (inbox-level listing vs. email-level reading vs. OTP extraction) explicit enough to avoid misselection.
All seven tools follow a consistent snake_case verb_noun pattern (create_inbox, delete_inbox, get_inbox, list_inboxes, read_email, wait_for_email, extract_codes). No deviations in casing or verb style.
Seven tools is well-scoped for a disposable email server, with each tool earning its place across the create/list/read/wait/extract/delete lifecycle. Nothing feels padded or redundant.
The surface covers the core lifecycle: create, list, get, delete inboxes, plus read, wait, and OTP extraction. Minor gaps exist (e.g., no delete_email, search, or forward, and no explicit attachment handling beyond read_email), but core workflows are fully supported.