Mektup-mcp
About
Mektup gives AI agents and their humans a real email mailbox, not just a one-way sending API. Through 41 MCP tools, an agent can register a domain, create a mailbox, send and receive mail, and manage threads, drafts, fol
Details
- Author
- WeeCi
- Downloads
- 291
- Categories
- Communication, Automation, Productivity, Developer Tools, AI
Jump to
- Full REST API reference — everything this server wraps
- OpenAPI 3.1 spec — machine-readable version of the same API
- usemektup.com — sign up, dashboard, pricing
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Mektup-mcpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
The README includes setup instructions such as "command": "node",.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mektup-mcp": {
"mektup": {
"url": "https://mcp.usemektup.com/mcp",
"headers": {
"Authorization": "Bearer mek_live_..."
}
}
}
}
}McpServers
{
"mektup": {
"url": "https://mcp.usemektup.com/mcp",
"headers": {
"Authorization": "Bearer mek_live_..."
}
}
}Every tool call is a straight HTTP call to the realMektup REST API. There's no separate logic to learn — if you understand the API, you understand the MCP server.Full coverage: every REST endpoint has a matching tool, verified with real read and write round-trips against the live production API (create → update → list → delete, confirmed at each step).
Two ways to run it, same tool set either way (lib/build-server.jsdefines the tools once, shared by both):
- Remote (Streamable HTTP)— a server we host athttps://mcp.usemektup.com/mcp. Point any client that takes a "custom MCP server" URL at it directly, no install. This is what Lovable/Cursor/Replit/Base44-style platforms want.
- Local (stdio)— runserver.jsyourself with your key in an env var. For MCP clients that only support launching a local process (Claude Desktop config, etc.).
Remote server (recommended for platform integrations)
Endpoint:https://mcp.usemektup.com/mcp(Streamable HTTP — supports both the direct-JSON-response and SSE-streaming response modes of the spec).
Stateless:no session is kept between requests — every tool call is already a one-shot passthrough to the REST API, so there's no session state worth keeping.
Tenant isolation:identical to the REST API, because itisthe REST API underneath — the server holds no account-specific credential itself, it just forwards whichever token the caller sent (API key or OAuth access token, see below) straight through toapi.usemektup.com, which is the only place that actually verifies it. A token only ever sees its own account's data.
Two auth modes, same endpoint, both arrive as the sameAuthorization: Bearer <token>header:
OAuth (recommended for platform integrations)
For a platform with real end users (Lovable, Cursor, Replit, Base44, ...) — the user clicks "connect," signs in with their existing Mektup account, approves, done. No token copy-paste, no dashboard visit.
Clerk (clerk.usemektup.com) is the OAuth 2.1 authorization server — this MCP server is only ever a resource server. Discovery is automatic for any spec-compliant OAuth-capable MCP client: it only needs the endpoint URL above and finds the rest itself viahttps://mcp.usemektup.com/.well-known/oauth-protected-resource/mcp(RFC 9728), which points at Clerk's ownhttps://clerk.usemektup.com/.well-known/oauth-authorization-server(RFC 8414). From there the client registers itself via Dynamic Client Registration (no manual setup needed on your end) and runs a standard Authorization Code + PKCE flow, ending with a JWT access token used exactly like an API key.
Lovable:Connectors → All →Custom(MCP card) → Server NameMektup, Server URLhttps://mcp.usemektup.com/mcp, Auth →OAuth(default when a server supports it) → Add & authorize.
API key (simplest for a single account, scripts, or a client without OAuth support)
Authorization: Bearer mek_live_...— create one atapp.usemektup.com→API keys.
Adding it to a client that supports custom MCP connectors is normally 3 fields:
Cursor / Claude Desktop / any client that reads raw MCP JSON config:
{ "mcpServers": { "mektup": { "url": "https://mcp.usemektup.com/mcp", "headers": { "Authorization": "Bearer mek_live_..." } } } }
Replit / Base44 / other "connect a tool" flows:same three fields as the table above — server URL, Bearer auth, key.
Use this when a client can only launch a local process, not call a remote URL.
git clone https://github.com/WeeCi/mektup-mcp.git cd mektup-mcp npm install
3. Configure your MCP clientto runserver.jswith the key as an environment variable. For Claude Desktop / Claude Code, add to your MCP config (e.g.claude_desktop_config.json):
{ "mcpServers": { "mektup": { "command": "node", "args": ["/absolute/path/to/mektup-mcp/server.js"], "env": { "MEKTUP_API_KEY": "mek_live_..." } } } }
MEKTUP_API_BASE_URLis optional and defaults tohttps://api.usemektup.com— no need to set it under normal use.
The server refuses to start withoutMEKTUP_API_KEYset.
Every tool returns its result as JSON text on success. On failure, it returnsisError: truewithError: <message>— the message is the same one the underlying REST endpoint returned (see theAPI referencefor exact error conditions, including billing-limit402s, per endpoint).
send_email({ from: "hello@example.com", to: "you@gmail.com", subject: "It works", text: "Real mail, sent through Mektup." }) → { "messageId": "<...@example.com>", "envelope": { "from": "hello@example.com", "to": ["you@gmail.com"] } }
- Full REST API reference— everything this server wraps
- OpenAPI 3.1 spec— machine-readable version of the same API
- usemektup.com— sign up, dashboard, pricing
Automate email tasks using SMTP and IMAP protocols.
Free disposable email for AI—check any @mailinator.com inbox, retrieve messages in multiple formats, and extract verification codes for automated workflows.
Sendmux serves AI-native startups, SaaS teams, automation agencies, and platform builders that need AI agents to send, receive, route, and react to email in production. Primary buyers and users include technical founders, founding engineers, backend engineers, platform engineers, AI automation consultants, support automation leads, ops teams, and growth teams using their own Gmail, Outlook, SMTP, or managed Amazon SES sending setup.
Manage notification workflows, users, preferences, and tenant branding via natural language. Trigger email, SMS, push, WhatsApp, Slack, and in-app notifications from Cursor, Claude Desktop, or Windsurf using 24 tools.
The MCP email server with human approval — AI drafts emails, you approve before they send. Works with Claude Code, Cursor, Windsurf, and any MCP client.
Zo is your personal vibe server in the cloud with 50+ tools and integrations. Add texting, email, calendar, research and more to your harness easily.
AI-powered CRM for small business sales teams with lead scoring, built-in dialer, WhatsApp/SMS, email automation, and forecasting.
A secure, no-code MCP server that connects any email inbox to AI assistants for intelligent reading, drafting, and automation.
Allow your agents to launch personalized outbound campaigns
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
