Email

Name: Email
Author: blipemail

blipemail/blip

1 repo stars
Updated March 24, 2026
blipemail/blip

Blip Email MCP is an MCP server that creates disposable inboxes, receives mail, and extracts OTP codes for testing.

About

The Blip Email MCP server wires disposable inboxes into Claude Code, Cursor, and other MCP clients so developers can test registration, magic links, and one-time passwords without manual inbox juggling. Typical use is testing: your agent creates a Blip address, waits for messages, and pulls OTP codes into automated checks for SaaS onboarding or CLI login flows. Distribution is npm @useblip/email at v0.1.3 with stdio transport; you must supply a Blip API key as BLIP_API_KEY. It is narrower than a full email marketing stack—focused on throwaway reception and code extraction for dev QA. Not a substitute for production transactional email providers.

Create disposable inboxes via Blip API through MCP
Receive emails and extract OTP codes for agent-driven test scripts
npm package @useblip/email (v0.1.3) with stdio MCP transport
Requires BLIP_API_KEY secret in environment
Lives in blipemail/blip repo subfolder mcp-server

Email by the numbers

Data as of Jul 7, 2026 (Skillselion catalog sync)

terminal

claude mcp add --env BLIP_API_KEY=YOUR_BLIP_API_KEY email -- npx -y @useblip/email

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/mcp/tool/io.github.blipemail/email.svg)](https://skillselion.com/mcp/tool/io.github.blipemail/email)

repo stars	★ 1
Package	@useblip/email
Transport	STDIO
Auth	Required
Last updated	March 24, 2026
Repository	blipemail/blip ↗

What it does

Spin up disposable Blip inboxes from your agent to test sign-up, email verification, and OTP flows without polluting your real mailbox.

Who is it for?

Best when you're shipping auth and want agent-driven E2E checks with disposable email.

Skip if: Production customer email, newsletters, or compliance-heavy enterprise mail without Blip’s disposable model.

What you get

Your agent can provision Blip inboxes and parse OTPs so sign-up and auth flows get repeatable automated tests.

On-demand disposable Blip inboxes for test runs
Received message content and parsed OTP codes inside agent workflows
Repeatable auth-path tests without a personal email account

By the numbers

npm package @useblip/email version 0.1.3
Required environment variable BLIP_API_KEY (secret)
Repository subfolder mcp-server under blipemail/blip on GitHub

README.md

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:

Component	License
`server/core`	AGPL-3.0
`mcp-server`	MIT
`cli`	MIT
`shared-models`	MIT

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.