MCP server for AI agents
Let an AI agent make its own email address, sign up somewhere, and read the verification code back without anyone copying and pasting.
The Mailfornet MCP server is a remote Model Context Protocol server. Any client that speaks MCP can use it, including Claude Desktop, Claude Code, Cursor, Windsurf, VS Code and your own agents. Nothing is installed. You give the client a URL and your API key.
| Server URL | https://api.mailfornet.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Auth | Authorization: Bearer mf_live_your_key |
| Billing | Each tool call is one API request, from the same quota as the REST API |
What an agent can do with it
A typical run, in the agent's own words: "I'll make an inbox, use it on the signup form, wait for the code, then enter it."
create_inboxreturns a fresh address such asryan.grant688@tikaurasave.site.- The agent fills in the signup form with it, using a browser tool.
wait_for_codeholds for up to a minute and returns{"code": "731905", "link": "https://…/verify?…"}. Newsletters and other mail without a code are skipped.- The agent types the code or opens the link.
delete_inboxcleans up. Otherwise the address expires by itself.
Tools
| Tool | What it does |
|---|---|
create_inbox | New address. Optional username, domain, ttl_minutes (1–1440). |
wait_for_code | Waits for a verification code or confirm link and returns it. Optional timeout_seconds, from, subject. |
list_messages | What has arrived, newest first. Optional wait_seconds, from, subject. |
read_message | One email as plain text, with its code and every link. HTML is stripped so it doesn't fill the model's context. |
delete_inbox | Deletes an address and its mail now. |
list_domains | Domains addresses can be created on. |
get_usage | Requests used this month and what is left. |
Claude Code
claude mcp add --transport http mailfornet https://api.mailfornet.com/mcp \
--header "Authorization: Bearer mf_live_your_key"
Claude Desktop
Settings → Developer → Edit config, then add:
{
"mcpServers": {
"mailfornet": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://api.mailfornet.com/mcp",
"--header", "Authorization: Bearer ${MAILFORNET_API_KEY}"
],
"env": { "MAILFORNET_API_KEY": "mf_live_your_key" }
}
}
}
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"mailfornet": {
"url": "https://api.mailfornet.com/mcp",
"headers": { "Authorization": "Bearer mf_live_your_key" }
}
}
}
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"mailfornet": {
"serverUrl": "https://api.mailfornet.com/mcp",
"headers": { "Authorization": "Bearer mf_live_your_key" }
}
}
}
VS Code
Add to .vscode/mcp.json. VS Code asks for the key once and stores it securely:
{
"inputs": [
{ "type": "promptString", "id": "mailfornet-key", "description": "Mailfornet API key", "password": true }
],
"servers": {
"mailfornet": {
"type": "http",
"url": "https://api.mailfornet.com/mcp",
"headers": { "Authorization": "Bearer ${input:mailfornet-key}" }
}
}
}
Your own agent
With the official TypeScript SDK:
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';
const client = new Client({ name: 'my-agent', version: '1.0.0' });
await client.connect(new StreamableHTTPClientTransport(new URL('https://api.mailfornet.com/mcp'), {
requestInit: { headers: { Authorization: `Bearer ${process.env.MAILFORNET_API_KEY}` } },
}));
const inbox = await client.callTool({ name: 'create_inbox', arguments: {} });
const { address } = inbox.structuredContent;
Keys and safety
- Use a separate key for each agent. Create one in your account, give it an expiry date, and revoke it when you're done. Nothing else is affected.
- Read-only keys work. A key with the
readscope can list and read mail but not create or delete inboxes. That suits an agent that should only watch. - Errors come back to the model. A wrong address or an exhausted quota returns a readable error, such as
inbox_not_foundorquota_exceeded, instead of breaking the session. The agent can see what went wrong and decide what to do. - Use it on sites that allow it. Signing up to test your own product, or trying a service, is fine. Mass account creation or getting around a site's rules is not. See our terms.
Next
The MCP tools sit on top of the REST API, so anything an agent does can also be done from ordinary code. Pricing has a free tier of 100 requests a month, which is enough to try it.