useblip/email
# @useblip/email
MCP server for [Blip](https://useblip.email) disposable email. Create inboxes, receive emails, and extract OTP codes — all from your AI agent.
## Setup
### Claude Desktop
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"blip": {
"command": "npx",
"args": ["-y", "@useblip/email"],
"env": {
"BLIP_API_KEY": "blip_ak_..."
}
}
}
}
```
### Claude Code
```bash
claude mcp add blip -- npx -y @useblip/email
```
Set your API key:
```bash
export BLIP_API_KEY=blip_ak_...
```
### Other MCP clients
Run the server directly:
```bash
BLIP_API_KEY=blip_ak_... npx @useblip/email
```
## Getting an API key
1. Sign in at [app.useblip.email](https://app.useblip.email)
2. Open [app.useblip.email/tokens](https://app.useblip.email/tokens) and create an API key
Any signed-in Blip account can create one key. The Agent tier gives unlimited keys.
## Tools
| Tool | Description |
|------|-------------|
| `create_inbox` | Create a disposable email inbox with optional custom slug, domain, and TTL |
| `list_inboxes` | List all active inboxes |
| `get_inbox` | Get inbox details and list of received emails |
| `read_email` | Read full email content (body, headers, attachments) |
| `extract_codes` | Extract OTP codes and verification links from the latest email |
| `wait_for_email` | Poll until an email arrives (configurable timeout, default 60s) |
| `delete_inbox` | Delete an inbox and all its emails |
## Example prompts
- "Create a disposable email and sign up for example.com, then give me the verification code"
- "Make an inbox, wait for the password reset email, and extract the link"
- "List my active inboxes and show me the latest emails"
## Environment variables
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `BLIP_API_KEY` | Yes | — | Your Blip API key |
| `BLIP_API_URL` | No | `https://api.useblip.email` | API base URL (for self-hosted) |
## License
[MIT](LICENSE)
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.