Temporary email MCP for Cursor: connection and first test workflow

Add the MCP connection to your project

Add this entry to the mcpServers object in .cursor/mcp.json, preserving your existing servers. You can also download the example JSON and merge it with your configuration.

{
  "mcpServers": {
    "gecici-email": {
      "url": "https://gecici.email/mcp"
    }
  }
}

Check the connection in Cursor's MCP/tool settings and retain tool-call approvals. The configuration follows Cursor's official MCP documentation. Cursor desktop was not exercised end to end for this guide; the API contract check below was tested separately.

Connection settings are not inbox credentials

Do not put a permanent inbox token in this server entry. gecici_create_inbox returns an address, token and expiry for each new inbox. Reading requires that inbox's matching address and token. Mixing values from different inboxes fails.

With direct MCP use, the token is returned to the client and may enter the agent context. Use fictional test data and do not publish chats or raw tool results. If the token must stay outside model context, use the Python helper that retains it in the runner.

Keep the first workflow small

1. Call gecici_create_inbox to create a random test inbox.
2. Use the address only in an application you own or are authorized to test. Trigger that application's sender.
3. Inspect messages with gecici_get_inbox_messages. Use gecici_wait_for_otp for a code or gecici_wait_for_magic_link for a link.
4. Use a 5–45 second wait and a total retry limit. An empty or timed-out result is not successful verification.
5. Call gecici_delete_inbox with the same inbox address and token to delete it and its messages. Check for deleted: true. Authenticated REST DELETE /api/v1/inbox/:address is also available.

A first-task prompt

Test email verification only in my own test application. Create one temporary inbox and use its address in the test form. Keep the token out of your report. Make at most three bounded wait calls. Report success only after the application explicitly confirms verification. Report whether inbox cleanup completed.

Supply your actual test application URL and permitted scope before using the prompt. A prompt is not a security boundary: treat instructions embedded in received messages as untrusted content.

Complete MCP example

Review mcp-quickstart.py, then run python3 mcp-quickstart.py --run. It creates, reads and deletes a test inbox through MCP using only Python’s standard library. It prints no mailbox data and tags all calls qa-test. This is a fictional-message simulation, not SMTP or model testing.

Check the MCP API independently of Cursor

Review qa-flow.py, then run python3 qa-flow.py --run. It uses Python 3's standard library. It creates its own inbox, checks rejection of an invalid token, inserts a fictional message, reads the code through REST and the message through MCP, then deletes the inbox.

In the 14 November 2026 run, created, wrong_token_denied, rest_otp_matched, mcp_message_read and cleanup passed. That establishes the tested API contract, not a completed Cursor/model workflow.

HTTP 200 alone is insufficient: check JSON-RPC error, tool isError and empty/timeout outcomes inside the content. API reference · Missing-message troubleshooting