Productivity · Remote MCP server
Mektup
Fully-managed email as MCP tools - register domains, real mailboxes, send and receive mail.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.WeeCi/mektup-mcp- Version
- 0.2.6
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-21
- Updated
- 2026-08-21
- Publisher
- WeeCi (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/WeeCi) · how
- Listed under
- Email MCP servers
- Website
- usemektup.com
- Repository
- github.com/WeeCi/mektup-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.usemektup.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Mektup
Mektup is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.usemektup.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| MeetingsCreate encrypted LIQAA video meetings; read plans, capacity & stats. No install, no account. | Remote · HTTPLive check: ✓ handshake |
| MeetNotesSearch, read and export MeetNotes meeting transcripts, minutes and action items (getmeetnotes.com). | Remote · HTTPLive check: sign-in required |
| MeetStreamMeeting bots for Zoom, Google Meet and Teams: record, transcribe, summarize, run voice agents. | Remote · HTTPLive check: sign-in required |
| MeetwhenFree no-signup group scheduling (a modern When2meet): share one link, find a time for everyone. | Remote · HTTPLive check: ✗ no handshake |
| Melt Peer ReviewSend AI-made document changes for human review, then read the decisions back. | Remote · HTTPLive check: sign-in required |
| MemSecurely search, create, and organize your Mem notes and collections from AI assistants. | Remote · HTTPLive check: sign-in required |
| MementoHosted MCP memory for coding agents: persistent across sessions, editable markdown, team sharing. | Remote · HTTPLive check: sign-in required |
| MemexLocal-first second brain with semantic search. Markdown notes indexed by a local ML model. | Local · stdio |