Mockmail Email Debugging Mcp Server

Created By

3 months ago

Connect Claude Code and other AI agents to Mockmail via the Model Context Protocol (MCP). Automatically test, verify, and debug emails during development without the risk of sending messages to real customers.

# Email

# Debugging

Overview Content Tools Comments

Overview

<link rel="stylesheet" type="text/css" href="/css/bootstrap.min.css">
<link href="/css/public.css" rel="stylesheet">

<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="shortcut icon" href="/favicon.ico" />
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />
<link rel="manifest" href="/site.webmanifest" />

<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/favicon-de/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">

<meta name="saashub-verification" content="pe2z5lu1pdgx">

  <link href="https://cdn.jsdelivr.net/npm/bootstrap-icons@1.11.3/font/bootstrap-icons.css" rel="stylesheet">

<script type="text/javascript">
    document.addEventListener('DOMContentLoaded', () => {
        // Tabs
        document.querySelectorAll('[role=tablist] a').forEach(a => {
            a.addEventListener('click', e => {
                e.defaultPrevented = true;
                e.preventDefault();

                // Hide other tabs
                document.querySelectorAll('.tab-pane').forEach(tab => {
                    tab.classList.remove('show');
                    tab.classList.remove('active');
                });

                // Mark tab link as active
                document.querySelectorAll('[role=tablist] .nav-link').forEach(l => {
                    l.classList.remove('active');
                });

                a.classList.add('active');

                let target = e.target.getAttribute('href');
                let tab = document.querySelector(target);
                tab.classList.add('show');
                tab.classList.add('active');

                return false;
            });
        });

        // Dropdowns
        document.querySelectorAll('[data-toggle=collapse]').forEach(a => {
            a.addEventListener('click', e => {
                e.defaultPrevented = true;
                e.preventDefault();

                let link = e.target.closest('a');
                let collapseTargetId = link.getAttribute('href');
                let collapseTarget = document.querySelector(collapseTargetId);

                let svg = link.querySelector('svg');

                if (collapseTarget.classList.contains('show')) {
                    svg.classList.remove('transform-rotate-90-deg');
                    collapseTarget.classList.remove('show');
                } else {
                    svg.classList.add('transform-rotate-90-deg');
                    collapseTarget.classList.add('show');
                }

                return false;
            });
        });

        const toggle = document.getElementById('navbar-toggle');
        let isExpanded = false;

        if (toggle) {
            toggle.addEventListener('click', () => {
                console.log('click!');
                const navMenu = document.getElementById('navigation-menu');
                isExpanded = !isExpanded;
                const show = navMenu.classList.toggle('show');

                toggle.setAttribute('aria-expanded', isExpanded);
            });
        }
    });
</script>

Documentation

Comprehensive guide to integrating Mockmail's REST API and MCP Server into your workflow

MCP Server
Overview
Installation
Available Tools

        <!-- REST API -->
        <li class="nav-item">
          <a class="nav-link parent" href="#rest-api">
            <i class="bi bi-cloud-arrow-up"></i> REST API
          </a>
        </li>
        <li class="nav-item">
          <a class="nav-link child" href="#rest-overview">Overview</a>
        </li>
        <li class="nav-item">
          <a class="nav-link child" href="#rest-api-keys">Generate API Keys</a>
        </li>
        <li class="nav-item">
          <a class="nav-link child" href="#rest-endpoints">Endpoints</a>
        </li>
        <li class="nav-item">
          <a class="nav-link child" href="#api-list-inboxes">List Inboxes</a>
        </li>
        <li class="nav-item">
          <a class="nav-link child" href="#api-list-emails">List Emails</a>
        </li>
        <li class="nav-item">
          <a class="nav-link child" href="#api-get-email">Get Email</a>
        </li>
      </ul>
    </nav>
  </div>

  <!-- Main Content -->
  <div class="col-md-9">
    <div class="docs-content">

      <!-- ============================================ -->
      <!-- MCP SERVER SECTION -->
      <!-- ============================================ -->

      <h2 id="mcp-server">
        <i class="bi bi-robot"></i> MCP Server
      </h2>

      <!-- MCP Overview -->
      <h3 id="mcp-overview">Overview</h3>
      <p>
        The Model Context Protocol (MCP) server allows AI tools and coding agents, such as Claude Code, to access your Mockmail inboxes and emails.
      </p>
      <p>
        This is particularly useful for AI assistants that need to verify and test emails automatically. Configure your application runtime to use your Mockmail virtual SMTP server and allow your coding agent to send emails from your development environment.
      </p>
      <p>
        Mockmail safely captures all outgoing emails. Your AI coding agent can then autonomously inspect, verify, and debug those emails through the Mockmail MCP server.
      </p>

      <!-- MCP Installation -->
      <h3 id="mcp-installation">Installation</h3>
      <p>
        To connect any AI coding agent to the Mockmail MCP Server, you first need to generate an API key.
      </p>

      <h4>1. Generate an API Key</h4>
      <p>
        Log in to your Mockmail account and navigate to <strong>API Keys</strong>. Click <strong>New API Key</strong> and give it a descriptive name.
        Copy the token immediately, as it will not be displayed again.
      </p>

      <div class="alert alert-warning">
        <i class="bi bi-exclamation-triangle"></i> <strong>Important:</strong> Store your API token securely.
        It provides full access to your inboxes and emails. Never commit tokens to version control.
      </div>

      <h4>2. Connect Claude Code</h4>
      <p class="mb-4">There are several ways to add the Mockmail MCP server to your Claude Code installation.</p>

      <h5>Option 1: Using the CLI (Recommended)</h5>
      <p>The easiest and fastest way is to open a terminal and run the following command:</p>
      <pre><code><span class="hl-keyword">claude</span> <span class="hl-string">mcp add</span> <span class="hl-operator">--transport</span> <span class="hl-string">http</span> <span class="hl-string">mockmail</span> <span class="hl-string">https://mockmail.io/mcp/mockmail</span> <span class="hl-operator">\

--header "Authorization: Bearer your-token"

Replace your-token with your API token from the Dashboard.

      <h5>Option 2: Manual Configuration in .claude.json</h5>
      <p>Alternatively, you can add the MCP server manually to your personal Claude settings file <code>~/.claude.json</code>:</p>
      <pre><code>{

"mcpServers": { "mockmail": { "type": "http", "url": "https://mockmail.io/mcp/mockmail", "headers": { "Authorization": "Bearer ${MOCKMAIL_API_KEY}" } } } }

Make sure to set your personal Mockmail API key as an environment variable named MOCKMAIL_API_KEY.

      <h4>3. Project-Specific Configuration</h4>
      <p>
        The previous methods enable the MCP server globally for all your projects.
        If you want to enable the MCP server only for a single project, create a <code>.mcp.json</code> file in your project directory with the following contents:
      </p>
      <pre><code>{

"mcpServers": { "mockmail": { "type": "http", "url": "https://mockmail.io/mcp/mockmail", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

Note: When using a project-specific MCP configuration, Claude will ask you to approve the MCP server at the start of each session.

      <!-- MCP Tools -->
      <h3 id="mcp-tools">Available Tools</h3>
      <p>The MCP server provides three tools:</p>

      <!-- List Inboxes Tool -->
      <h4><i class="bi bi-inbox"></i> list-inboxes</h4>
      <p>Lists all inboxes accessible to the authenticated user.</p>

      <h5>Parameters</h5>
      <p class="text-muted">No parameters required</p>

      <h5>Example Request</h5>
      <pre><code>{

"jsonrpc": "2.0", "method": "tools/call", "params": { "name": "list-inboxes", "arguments": {} }, "id": 3 }

      <h5>Example Response</h5>
      <pre><code>{

"success": true, "count": 2, "inboxes": [ { "id": 1, "name": "Development Inbox", "username": "inbox_abc123", "email_count": 42, "email_limit": 100, "webhook_endpoint": "https://example.com/webhook", "created_at": "2024-01-15T10:30:00Z", "updated_at": "2024-03-07T14:22:00Z" } ] }

      <h5 class="mt-4">Response Fields</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Field</th>
            <th>Type</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>success</code></td>
            <td>boolean</td>
            <td>Indicates whether the request was successful</td>
          </tr>
          <tr>
            <td><code>count</code></td>
            <td>integer</td>
            <td>Number of inboxes returned</td>
          </tr>
          <tr>
            <td><code>inboxes</code></td>
            <td>array</td>
            <td>Array of inbox objects</td>
          </tr>
          <tr>
            <td><code>inboxes[].id</code></td>
            <td>integer</td>
            <td>Unique inbox ID</td>
          </tr>
          <tr>
            <td><code>inboxes[].name</code></td>
            <td>string</td>
            <td>Display name of the inbox</td>
          </tr>
          <tr>
            <td><code>inboxes[].username</code></td>
            <td>string</td>
            <td>SMTP/IMAP username for the inbox</td>
          </tr>
          <tr>
            <td><code>inboxes[].email_count</code></td>
            <td>integer</td>
            <td>Current number of emails in the inbox</td>
          </tr>
          <tr>
            <td><code>inboxes[].email_limit</code></td>
            <td>integer</td>
            <td>Maximum number of emails allowed</td>
          </tr>
        </tbody>
      </table>

      <!-- List Emails Tool -->
      <h4><i class="bi bi-envelope"></i> list-emails</h4>
      <p>Lists emails from a specific inbox with optional pagination and search.</p>

      <h5>Parameters</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Parameter</th>
            <th>Type</th>
            <th>Required</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>inbox_id</code></td>
            <td>integer</td>
            <td>Yes</td>
            <td>The ID of the inbox to retrieve emails from</td>
          </tr>
          <tr>
            <td><code>offset</code></td>
            <td>integer</td>
            <td>No</td>
            <td>Number of emails to skip (for pagination). Default: 0</td>
          </tr>
          <tr>
            <td><code>limit</code></td>
            <td>integer</td>
            <td>No</td>
            <td>Maximum number of emails to retrieve (1-100). Default: 10</td>
          </tr>
          <tr>
            <td><code>query</code></td>
            <td>string</td>
            <td>No</td>
            <td>Search query to filter emails by subject</td>
          </tr>
        </tbody>
      </table>

      <h5>Example Request</h5>
      <pre><code>{

"jsonrpc": "2.0", "method": "tools/call", "params": { "name": "list-emails", "arguments": { "inbox_id": 1, "limit": 5, "offset": 0, "query": "password reset" } }, "id": 4 }

      <h5 class="mt-4">Example Response</h5>
      <pre><code>{

"success": true, "inbox_id": 1, "total": 42, "offset": 0, "limit": 5, "count": 5, "emails": [ { "id": 123, "subject": "Password Reset Request", "excerpt": "Click the link below to reset your password...", "date": "2024-03-07T10:30:00Z", "from_name": "Support Team", "from_address": "support@example.com", "to_address": "user@test.com", "read": false, "attachments": [] } ] }

      <!-- Get Email Content Tool -->
      <h4><i class="bi bi-file-text"></i> get-email-content</h4>
      <p>Retrieves the full content of a specific email in HTML or plain text format.</p>

      <h5>Parameters</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Parameter</th>
            <th>Type</th>
            <th>Required</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>inbox_id</code></td>
            <td>integer</td>
            <td>Yes</td>
            <td>The ID of the inbox containing the email</td>
          </tr>
          <tr>
            <td><code>email_id</code></td>
            <td>integer</td>
            <td>Yes</td>
            <td>The ID of the email to retrieve</td>
          </tr>
          <tr>
            <td><code>format</code></td>
            <td>string</td>
            <td>No</td>
            <td>Content format: "html" or "plain". Default: "html"</td>
          </tr>
        </tbody>
      </table>

      <h5>Example Request</h5>
      <pre><code>{

"jsonrpc": "2.0", "method": "tools/call", "params": { "name": "get-email-content", "arguments": { "inbox_id": 1, "email_id": 123, "format": "html" } }, "id": 5 }

      <h5 class="mt-4">Example Response</h5>
      <pre><code>{

"success": true, "email": { "id": 123, "subject": "Password Reset Request", "from_name": "Support Team", "from_address": "support@example.com", "to_address": "user@test.com", "date": "2024-03-07T10:30:00Z", "read": false, "format": "html", "content": "<html><body><p>Click the link...</p></body></html>", "inbox": { "id": 1, "name": "Development Inbox" }, "attachments": [ { "id": 456, "cid": null, "filename": "invoice.pdf", "content_type": "application/pdf", "size": 45678 } ] } }

      <!-- ============================================ -->
      <!-- REST API SECTION -->
      <!-- ============================================ -->

      <h2 id="rest-api">
        <i class="bi bi-cloud-arrow-up"></i> REST API
      </h2>

      <!-- REST Overview -->
      <h3 id="rest-overview">Overview</h3>
      <p>
        The REST API provides HTTP endpoints for accessing your Mockmail data.
        All endpoints are prefixed with <code>/api/v1</code> and require
        authentication via Bearer token.
      </p>

      <h4>Base URL</h4>
      <div class="endpoint">
        https://mockmail.io/api/v1
      </div>

      <h4>Response Format</h4>
      <p>All API responses are in JSON format with the following structure:</p>
      <pre><code>{

"success": true, "data": { ... } }

      <h4>Error Responses</h4>
      <p>Error responses contain an error message:</p>
      <pre><code>{

"success": false, "error": "Error description" }

      <h4>HTTP Status Codes</h4>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Code</th>
            <th>Meaning</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>200</code></td>
            <td>Success</td>
          </tr>
          <tr>
            <td><code>401</code></td>
            <td>Unauthorized - Invalid or missing API token</td>
          </tr>
          <tr>
            <td><code>403</code></td>
            <td>Forbidden - No permission for this resource</td>
          </tr>
          <tr>
            <td><code>404</code></td>
            <td>Not Found - Resource does not exist</td>
          </tr>
          <tr>
            <td><code>422</code></td>
            <td>Validation Error - Invalid input parameters</td>
          </tr>
        </tbody>
      </table>

      <!-- REST API Keys -->
      <h3 id="rest-api-keys">Generate API Keys</h3>
      <p>
        All API requests require authentication using Laravel Sanctum API tokens.
      </p>

      <h4>Create a Token</h4>
      <ol>
        <li>Log in to your Mockmail account at <a href="/app">/app</a></li>
        <li>Navigate to <strong>Settings</strong> → <strong>API Keys</strong></li>
        <li>Click <strong>"Create New API Key"</strong></li>
        <li>Give your token a descriptive name (e.g., "Production Integration")</li>
        <li>Copy the token immediately - it will only be shown once</li>
      </ol>

      <div class="alert alert-warning">
        <i class="bi bi-exclamation-triangle"></i> <strong>Important:</strong> Store your API token securely.
        It provides full access to your inboxes and emails. Never commit tokens to version control.
      </div>

      <h4>Use the Token</h4>
      <p>Include your token in the <code>Authorization</code> header of all requests:</p>
      <pre><code>Authorization: Bearer YOUR_API_TOKEN_HERE</code></pre>

      <!-- REST Endpoints -->
      <h3 id="rest-endpoints">API Endpoints</h3>

      <!-- List Inboxes Endpoint -->
      <h4 id="api-list-inboxes">
        <span class="badge badge-method">GET</span> /api/v1/inboxes
      </h4>
      <p>Retrieves all inboxes accessible to the authenticated user.</p>

      <h5 class="mt-4">Request</h5>
      <pre><code>GET /api/v1/inboxes HTTP/1.1

Host: localhost:8000 Authorization: Bearer YOUR_API_TOKEN_HERE Accept: application/json

      <h5 class="mt-4">Response</h5>
      <pre><code>{

"success": true, "data": [ { "id": 1, "name": "Development Inbox", "email_count": 42, "email_limit": 100, "username": "inbox_abc123", "password": "secure_password", "email_username": "custom@mockmail.io", "enable_email_username": true, "webhook_endpoint": "https://example.com/webhook", "enable_webhook": true, "created_at": "2024-01-15T10:30:00.000000Z", "updated_at": "2024-03-07T14:22:00.000000Z" }, { "id": 2, "name": "Staging Inbox", "email_count": 15, "email_limit": 50, "username": "inbox_xyz789", "password": "another_password", "email_username": null, "enable_email_username": false, "webhook_endpoint": null, "enable_webhook": false, "created_at": "2024-02-01T08:15:00.000000Z", "updated_at": "2024-03-05T11:45:00.000000Z" } ] }

      <h5 class="mt-4">cURL Example</h5>
      <pre><code>curl -X GET https://mockmail.io/api/v1/inboxes \

-H "Authorization: Bearer YOUR_API_TOKEN_HERE"
-H "Accept: application/json"

      <h5 class="mt-4">Response Fields</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Field</th>
            <th>Type</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>id</code></td>
            <td>integer</td>
            <td>Unique inbox ID</td>
          </tr>
          <tr>
            <td><code>name</code></td>
            <td>string</td>
            <td>Display name of the inbox</td>
          </tr>
          <tr>
            <td><code>email_count</code></td>
            <td>integer</td>
            <td>Current number of emails in the inbox</td>
          </tr>
          <tr>
            <td><code>email_limit</code></td>
            <td>integer</td>
            <td>Maximum number of emails allowed in the inbox</td>
          </tr>
          <tr>
            <td><code>username</code></td>
            <td>string</td>
            <td>SMTP/IMAP username for this inbox</td>
          </tr>
          <tr>
            <td><code>password</code></td>
            <td>string</td>
            <td>SMTP/IMAP password for this inbox</td>
          </tr>
          <tr>
            <td><code>email_username</code></td>
            <td>string|null</td>
            <td>Custom email username if enabled</td>
          </tr>
          <tr>
            <td><code>enable_email_username</code></td>
            <td>boolean</td>
            <td>Whether custom email username is enabled</td>
          </tr>
          <tr>
            <td><code>webhook_endpoint</code></td>
            <td>string|null</td>
            <td>Webhook URL for email notifications</td>
          </tr>
          <tr>
            <td><code>enable_webhook</code></td>
            <td>boolean</td>
            <td>Whether webhook notifications are enabled</td>
          </tr>
          <tr>
            <td><code>created_at</code></td>
            <td>string</td>
            <td>ISO 8601 timestamp when the inbox was created</td>
          </tr>
          <tr>
            <td><code>updated_at</code></td>
            <td>string</td>
            <td>ISO 8601 timestamp when the inbox was last updated</td>
          </tr>
        </tbody>
      </table>

      <!-- List Emails Endpoint -->
      <h4 class="mt-5" id="api-list-emails">
        <span class="badge bg-success badge-method">GET</span> /api/v1/inboxes/{id}/emails
      </h4>
      <p>Retrieves all emails from a specific inbox with optional pagination and search.</p>

      <h5>URL Parameters</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Parameter</th>
            <th>Type</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>id</code></td>
            <td>integer</td>
            <td>The ID of the inbox to retrieve emails from</td>
          </tr>
        </tbody>
      </table>

      <h5>Query Parameters</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Parameter</th>
            <th>Type</th>
            <th>Required</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>offset</code></td>
            <td>integer</td>
            <td>No</td>
            <td>Number of emails to skip (for pagination). Default: 0</td>
          </tr>
          <tr>
            <td><code>limit</code></td>
            <td>integer</td>
            <td>No</td>
            <td>Maximum number of emails to retrieve (1-100). Default: 10</td>
          </tr>
          <tr>
            <td><code>query</code></td>
            <td>string</td>
            <td>No</td>
            <td>Search query to filter emails by subject</td>
          </tr>
        </tbody>
      </table>

      <h5 class="mt-4">Request</h5>
      <pre><code>GET /api/v1/inboxes/1/emails?limit=5&offset=0&query=password%20reset HTTP/1.1

Host: localhost:8000 Authorization: Bearer YOUR_API_TOKEN_HERE Accept: application/json

      <h5 class="mt-4">Response</h5>
      <pre><code>{

"success": true, "data": { "inbox_id": 1, "total": 42, "offset": 0, "limit": 5, "count": 5, "emails": [ { "id": 123, "subject": "Password Reset Request", "date": "2024-03-07T10:30:00Z", "from_name": "Support Team", "from_address": "support@example.com", "to_address": "user@test.com" } ] } }

      <h5 class="mt-4">cURL Example</h5>
      <pre><code>curl -X GET "https://mockmail.io/api/v1/inboxes/1/emails?limit=10&offset=0" \

-H "Authorization: Bearer YOUR_API_TOKEN_HERE"
-H "Accept: application/json"

      <h5 class="mt-4">Response Fields</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Field</th>
            <th>Type</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>inbox_id</code></td>
            <td>integer</td>
            <td>ID of the inbox the emails belong to</td>
          </tr>
          <tr>
            <td><code>total</code></td>
            <td>integer</td>
            <td>Total number of emails available in the inbox (matching search query if provided)</td>
          </tr>
          <tr>
            <td><code>offset</code></td>
            <td>integer</td>
            <td>Pagination offset used for the query</td>
          </tr>
          <tr>
            <td><code>limit</code></td>
            <td>integer</td>
            <td>Maximum number of emails requested</td>
          </tr>
          <tr>
            <td><code>count</code></td>
            <td>integer</td>
            <td>Number of emails returned in this response</td>
          </tr>
          <tr>
            <td><code>emails</code></td>
            <td>array</td>
            <td>Array of email objects</td>
          </tr>
          <tr>
            <td><code>emails[].id</code></td>
            <td>integer</td>
            <td>Unique email ID</td>
          </tr>
          <tr>
            <td><code>emails[].subject</code></td>
            <td>string</td>
            <td>Email subject</td>
          </tr>
          <tr>
            <td><code>emails[].date</code></td>
            <td>string</td>
            <td>ISO 8601 timestamp when the email was received</td>
          </tr>
          <tr>
            <td><code>emails[].from_name</code></td>
            <td>string</td>
            <td>Sender display name</td>
          </tr>
          <tr>
            <td><code>emails[].from_address</code></td>
            <td>string</td>
            <td>Sender email address</td>
          </tr>
          <tr>
            <td><code>emails[].to_address</code></td>
            <td>string</td>
            <td>Recipient email address</td>
          </tr>
        </tbody>
      </table>

      <!-- Get Email Endpoint -->
      <h4 class="mt-5" id="api-get-email">
        <span class="badge bg-success badge-method">GET</span> /api/v1/emails/{id}
      </h4>
      <p>Retrieve a single email with all its details, including HTML/plain text content and attachments.</p>

      <h5>Path Parameters</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Parameter</th>
            <th>Type</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>id</code></td>
            <td>integer</td>
            <td>The ID of the email to retrieve</td>
          </tr>
        </tbody>
      </table>

      <h5>Request Example</h5>
      <pre><code>GET /api/v1/emails/123 HTTP/1.1

Host: mockmail.io Authorization: Bearer YOUR_API_TOKEN_HERE Accept: application/json

      <h5 class="mt-4">Response</h5>
      <pre><code>{

"success": true, "data": { "id": 123, "subject": "Password Reset Request", "date": "2024-03-15T14:30:00.000000Z", "from_name": "Support Team", "from_address": "support@example.com", "to_address": "inbox_abc123@mockmail.io", "inbox_id": 1, "html": "<html><body><p>Click here to reset your password</p></body></html>", "text": "Click here to reset your password", "attachments": [ { "id": 45, "filename": "logo.png", "content_type": "image/png", "size": 15234, "cid": "logo@example.com" } ] } }

      <h5 class="mt-4">cURL Example</h5>
      <pre><code>curl -X GET "https://mockmail.io/api/v1/emails/123" \

-H "Authorization: Bearer YOUR_API_TOKEN_HERE"
-H "Accept: application/json"

      <h5 class="mt-4">Response Fields</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Field</th>
            <th>Type</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>id</code></td>
            <td>integer</td>
            <td>Unique email ID</td>
          </tr>
          <tr>
            <td><code>subject</code></td>
            <td>string</td>
            <td>Email subject</td>
          </tr>
          <tr>
            <td><code>date</code></td>
            <td>string</td>
            <td>ISO 8601 timestamp when the email was received</td>
          </tr>
          <tr>
            <td><code>from_name</code></td>
            <td>string</td>
            <td>Sender display name</td>
          </tr>
          <tr>
            <td><code>from_address</code></td>
            <td>string</td>
            <td>Sender email address</td>
          </tr>
          <tr>
            <td><code>to_address</code></td>
            <td>string</td>
            <td>Recipient email address</td>
          </tr>
          <tr>
            <td><code>inbox_id</code></td>
            <td>integer</td>
            <td>ID of the inbox this email belongs to</td>
          </tr>
          <tr>
            <td><code>html</code></td>
            <td>string|null</td>
            <td>HTML content of the email (if available)</td>
          </tr>
          <tr>
            <td><code>text</code></td>
            <td>string|null</td>
            <td>Plain text content of the email (if available)</td>
          </tr>
          <tr>
            <td><code>attachments</code></td>
            <td>array</td>
            <td>Array of attachment objects</td>
          </tr>
          <tr>
            <td><code>attachments[].id</code></td>
            <td>integer</td>
            <td>Unique attachment ID</td>
          </tr>
          <tr>
            <td><code>attachments[].filename</code></td>
            <td>string</td>
            <td>Name of the attachment file</td>
          </tr>
          <tr>
            <td><code>attachments[].content_type</code></td>
            <td>string</td>
            <td>MIME type of the attachment (e.g., "image/png", "application/pdf")</td>
          </tr>
          <tr>
            <td><code>attachments[].size</code></td>
            <td>integer</td>
            <td>Size of the attachment in bytes</td>
          </tr>
          <tr>
            <td><code>attachments[].cid</code></td>
            <td>string</td>
            <td>Content-ID for inline attachments (used in HTML emails)</td>
          </tr>
        </tbody>
      </table>

      <h5>Error Responses</h5>
      <table class="table table-sm table-bordered">
        <thead>
          <tr>
            <th>Status Code</th>
            <th>Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td><code>401</code></td>
            <td>Unauthorized - Invalid or missing API token</td>
          </tr>
          <tr>
            <td><code>403</code></td>
            <td>Forbidden - You don't have permission to access this email</td>
          </tr>
          <tr>
            <td><code>404</code></td>
            <td>Not Found - Email does not exist</td>
          </tr>
        </tbody>
      </table>

    </div>
  </div>
</div>

Try in Playground

Server Config

{
  "mcpServers": {
    "mockmail": {
      "type": "http",
      "url": "https://mockmail.io/mcp/mockmail",
      "headers": {
        "Authorization": "Bearer ${MOCKMAIL_API_KEY}"
      }
    }
  }
}

Project Info

Created At

3 months ago

Updated At

3 months ago

Author Name

Star

Language

License

Recommend Servers

View All

mcp-server-flomo MCP Server

@chatmcp

Write notes to Flomo

JavaScript

a year ago

Mcp360 Universal Gateway

@mcp360

A universal gateway MCP server providing seamless integration with multiple AI models and services through a unified interface.

2 hours ago

Agentdrive

@Rakesh1002

AgentDrive is a cross-agent artifact workspace with provenance and portable storage across Claude Code, Codex, Cursor, and LangGraph. 20 MCP tools: file CRUD, semantic recall over workspace artifacts, run logging, cross-agent attribution, comments, and shares. Connect to the hosted server at https://mcp.agentdrive.sh/mcp with an Authorization: Bearer key, or run locally via npx @adrive/mcp-server. Free tier (1 GB + 10k embeddings) at https://app.agentdrive.sh — no credit card.

43 minutes ago

PostgreSQL

@modelcontextprotocol

Read-only database access with schema inspection

a year ago

Tavily Mcp

@tavily-ai

JavaScript

a year ago

Test

@modelcontextprotocol

test

6 months ago

Budget Governor

@mightbesaad

Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).

2 days ago

Krimto

@krimto-labs

Open-source memory for AI coding agents. Tell your agent to "remember" something in Cursor, Claude Code, Codex, or Gemini CLI, and Krimto saves it as a plain markdown file in a git repo you own — not rows in a vendor's database. Recall it later in a new chat, a different editor, or on another machine. One npx command, no account, no API key. Apache-2.0, with a user → team → org scope hierarchy so a team can share memory while personal notes stay private. Run: npx @krimto-labs/krimto init

a day ago

Nable (finops Mcp)

@chaandannn

Local-first FinOps copilot: ask about your AWS, Azure, GCP, and SaaS costs in plain English. Anomaly detection, rightsizing, idle-resource cleanup, and Jira/Linear ticketing, all in your own Claude. Credentials never leave your machine.

10 hours ago

Neural-OS

@Timwal78

Neural-OS — The mobile-first AI agent OS. Featuring sovereign agent tools for DePIN compute arbitrage, data bounty hunting, enterprise lead bartering, and live crypto pricing execution.

7 hours ago

Pet And Veterinary Products Recall

@agentprolabs

An open-source MCP server that makes government pet-food and veterinary-drug recall data queryable by AI assistants. Search and filter active recalls, fuzzy-match a specific product, and subscribe to email alerts — sourced daily from the Government of Canada (CFIA) and the US FDA (OpenFDA). Zero config: just npx.

8 hours ago

Framelink Figma MCP Server

@GLips

MCP server to provide Figma layout information to AI coding agents like Cursor

TypeScript

a year ago

Jina AI MCP Tools

@PsychArch

A Model Context Protocol (MCP) server that integrates with Jina AI Search Foundation APIs.

JavaScript

a year ago

SEO & GEO by OpenHelm

@Max Beech

Improve your visibility across both traditional search engines and AI-powered answer engines using a virtual computer that can analyse websites, competitors, content, and search performance. SEO & GEO by OpenHelm enables your agent to carry out work such as: • SEO audits and recommendations • GEO (Generative Engine Optimisation) analysis • Competitor monitoring • Content opportunity discovery • Search visibility reporting What makes OpenHelm the best solution for this: • Continuously evaluates whether recommendations are actually improving visibility over time • Can investigate competitors and search results using a highly capable stealth browser • Multi-step workflows allow analysis, planning, implementation, and monitoring to work together • Designed for both search engines and emerging AI discovery platforms For organisations looking to grow organic visibility, OpenHelm provides a secure environment where optimisation work can be performed continuously and autonomously.

3 hours ago

Madeonsol — Solana Kol & Memecoin Intelligence

@LamboPoewert

Real-time Solana memecoin intelligence for AI agents and trading bots — KOL wallet trades, Pump.fun deployer reputation, token quality scoring, wallet PnL, and pre-confirm launch alerts. 40+ tools. Free API key, or pay-per-call via x402.

17 hours ago

Neon MCP Server

@neondatabase-labs

MCP server for interacting with Neon Management API and databases

TypeScript

a year ago

MCP Advisor

@istarwyh

MCP Advisor & Installation - Use the right MCP server for your needs

TypeScript

a year ago

Hypd Ai Openai Ads

@HYPD-AI

Enable AI agents such as Claude, Co-Pilot, Codex, and other compatible tools to create, manage, and optimize advertising campaigns on ChatGPT.

2 days ago

Agent Tools Mcp

@AgentTools-Cloud

Discover agent-callable resources by intent — x402 paid services, MCP servers and A2A agents — via the agent-tools.cloud directory. 9 tools: search/get/list_categories (x402), search_mcp_servers/get_mcp_server, search_agents/get_agent, search_all, stats.

5 hours ago

Filesystem

@modelcontextprotocol

2 months ago

Firecrawl Mcp Server

@mendableai

Official Firecrawl MCP Server - Adds powerful web scraping to Cursor, Claude and any other LLM clients.

JavaScript

a year ago

Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.

@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago

虎嗅嗅 AI行业参谋

@虎嗅

虎嗅嗅官方AI助手，可查询AI行业早报、投融资事件、产品动态、硬件与原生关键信号。

3 hours ago

AI Work Market — USDC settlement rails for AI labor on Base Mainnet)

@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago

Devvyboard Developer Kanban, Task Management And Chat

@Stockulate LTD

Connect Cursor, Claude Desktop, and Codex to your Devvyboard workspace. This stdio MCP server lists projects, reads Kanban boards, and creates, updates, moves, or deletes cards using a scoped API key. Requires Devvyboard Pro and Node.js 20+.

16 hours ago

Agent Knowledge

@Ddhjx-code

AI Agent 岗位模拟面试 MCP Server —— 基于 FAISS + bge-base-zh-v1.5 构建的 RAG 知识库，为 AI Agent 技术面试提供语义检索、分级题库和个性化学习路径。

a day ago

Mcp Server Chatsum

@chatmcp

summarize chat message

typescript

a year ago

Github

@modelcontextprotocol

Repository management, file operations, and GitHub API integration

a year ago

Terraform Rag

@krzysztofgawrys

AI-powered knowledge base for your Terraform modules. Index, search, compose, and audit - all from one place.

19 hours ago

Modal MCP

@george-bobby

An MCP server for managing Modal — apps, containers, volumes, and secrets — and for deploying & running Modal apps directly from Claude Code and other MCP clients. Every tool shells out to your local modal CLI, so it operates against whatever Modal profile and credentials are configured on your machine. There are no extra tokens to manage.

7 hours ago