Lockally Email

com.lockallyPublished by lockally.comOfficial publisherv1.0.1Updated Oct 24, 2026

Stateful email for AI agents — read inboxes, reply in-thread, draft with approval.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that gives AI assistants stateful email: reading inboxes, replying within threads, and drafting messages for approval.

What you can do
Read inboxes and review incoming email statefully through the assistant session. Reply within existing email threads. Draft messages that are held for approval before sending. Access is authenticated with a Lockally API key, with separate live and test key forms.
When to use it
Useful when an assistant needs to work with real email conversations rather than one-off sends — triaging an inbox, continuing a thread, or preparing replies and drafts that a person reviews before they go out.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. A Lockally account and API key are required, sent as a Bearer token in the Authorization header. The key may be a live key or a test key.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared configurations. A live key can act on real mailboxes, so reading inboxes and replying in-thread touch private correspondence and send messages on the user's behalf. Drafts are described as requiring approval, but confirm that sending is gated before relying on it.

Installation

In SourceWeft

  1. Open Lockally Email in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.lockally%2Femail/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lockally-email": {
      "type": "http",
      "url": "https://mcp.lockally.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.