io.github.blipemail/email
MCP server for Blip disposable email — create inboxes, receive emails, extract OTP codes
What can you do with io.github.blipemail/email?
- Disposable email addresses with random or custom slugs
- Real-time email delivery via SSE
- OTP and verification link extraction
- Webhooks with HMAC-SHA256 signatures and delivery logs
- CLI for terminal workflows
- MCP server for AI agents
- Multi-domain support
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@useblip/emailclaude mcp add email -e 'BLIP_API_KEY=<your blip_api_key>' -- npx -y @useblip/email@0.1.3
{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@useblip/email@0.1.3"
],
"env": {
"BLIP_API_KEY": "<your blip_api_key>"
}
}
}
}
Environment variables
BLIP_API_KEYrequired secret Your Blip API key
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
blip
Instant disposable email inboxes. API, CLI, MCP server, and web app.
useblip.email | Docs | API Reference
Features
- Disposable email addresses with random or custom slugs
- Real-time email delivery via SSE
- OTP and verification link extraction
- Webhooks with HMAC-SHA256 signatures and delivery logs
- CLI for terminal workflows
- MCP server for AI agents
- Multi-domain support
Architecture
blip/
server/core/ Kotlin/Ktor API server (AGPL-3.0)
cli/ Kotlin/Clikt CLI
mcp-server/ TypeScript MCP server (npm: @useblip/email)
shared-models/ Shared Kotlin data models
Quickstart
Managed (useblip.email)
No setup required. Create inboxes at app.useblip.email or via the API:
# Get a session token
curl -X POST https://api.useblip.email/v1/sessions
# Create an inbox
curl -X POST https://api.useblip.email/v1/inboxes \
-H "Authorization: Bearer <token>"
CLI
brew install bmcreations/tap/blip
blip create
blip inbox --watch
Self-hosted
Prerequisites: JDK 21+, libSQL (sqld)
git clone https://github.com/blipemail/blip.git
cd blip
./gradlew :server:core:buildFatJar
# Start libSQL
sqld --http-listen-addr 127.0.0.1:8081 &
# Run the server
TURSO_URL=http://localhost:8081 WORKER_SECRET=dev-secret \
java -jar server/core/build/libs/*-all.jar
Or with Docker:
docker build -t blip .
docker run -p 8080:8080 \
-e TURSO_URL=http://host.docker.internal:8081 \
-e WORKER_SECRET=your-secret \
blip
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
PORT | No | 8080 | Server port |
TURSO_URL | Yes | http://localhost:8081 | libSQL/Turso database URL |
TURSO_AUTH_TOKEN | No | — | Turso auth token (production) |
WORKER_SECRET | Yes | dev-secret | Shared secret for authenticating inbound email delivery |
FRONTEND_URL | No | http://localhost:4321 | Frontend URL for CORS |
Development
See CONTRIBUTING.md for development setup and contribution guidelines.
# Run tests
./gradlew :server:core:test
# Build CLI
./gradlew :cli:installDist
./cli/build/install/cli/bin/cli --help
# Build MCP server
cd mcp-server && npm install && npm run build
License
This repository uses per-component licensing:
The API server is AGPL-3.0 to ensure modifications to the hosted service remain open source. The MCP server, CLI, and shared models are MIT for maximum adoption flexibility.
Frequently asked questions
What is io.github.blipemail/email?
MCP server for Blip disposable email — create inboxes, receive emails, extract OTP codes
How do I install io.github.blipemail/email?
It runs on your machine. In Claude Code: claude mcp add email -e 'BLIP_API_KEY=<your blip_api_key>' -- npx -y @useblip/email@0.1.3. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.blipemail/email need an API key?
Yes. It expects BLIP_API_KEY, which you set in its configuration.
Is io.github.blipemail/email open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.blipemail/email?
It is published by blipemail. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.