Email

io.github.blipemailPublished by GitHub account blipemailv0.1.3Updated Oct 27, 2026

MCP server for Blip disposable email — create inboxes, receive emails, extract OTP codes

VerifiedSTDIODesktop onlyDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Blip disposable email MCP server that lets an assistant create throwaway inboxes, read incoming mail, and pull out OTP codes and verification links.

What you can do
  • Create, list, inspect and delete disposable inboxes, with optional custom slug, domain and TTL
  • Read received emails in full, including body, headers and attachments
  • Extract OTP codes and verification links from the latest email
  • Poll until a new email arrives, with a configurable timeout (60s by default)
When to use it
Useful when an assistant needs a temporary address to receive sign-up confirmations, password reset messages or one-time codes during testing or automated flows, and to hand back the code or link without a human checking a mailbox.
Requirements
Runs locally via npx from the npm package @useblip/email (Node.js required). Needs a Blip account and an API key supplied in the BLIP_API_KEY environment variable; keys are created from the Blip web app. Network access to the Blip API is required, and BLIP_API_URL can point at a self-hosted instance.
Before you install
Requires the BLIP_API_KEY secret, which grants access to the account's inboxes. Inboxes and their emails can be deleted permanently through the server. Disposable inboxes are not private storage, and messages received there pass through Blip's service. Creating inboxes may be subject to account tier limits.

Installation

In SourceWeft

  1. Open Email in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@useblip/email

MCP server for Blip 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
  2. Open 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

ToolDescription
create_inboxCreate a disposable email inbox with optional custom slug, domain, and TTL
list_inboxesList all active inboxes
get_inboxGet inbox details and list of received emails
read_emailRead full email content (body, headers, attachments)
extract_codesExtract OTP codes and verification links from the latest email
wait_for_emailPoll until an email arrives (configurable timeout, default 60s)
delete_inboxDelete 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

VariableRequiredDefaultDescription
BLIP_API_KEYYes—Your Blip API key
BLIP_API_URLNohttps://api.useblip.emailAPI base URL (for self-hosted)

License

MIT

Source: mcp-server/README.md at commit d8510b4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.