JustEmails

app.justemailsPublished by justemails.appOfficial publisherv0.2.0Updated Oct 24, 2026

Email hosting from your AI: read and send mail, add domains, check DNS and manage mailboxes.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server for JustEmails that lets an assistant read and send mail, add domains, check DNS and manage mailboxes.

What you can do
Read and send email messages. Add domains and check their DNS settings. Manage mailboxes. All actions go through the JustEmails email hosting service.
When to use it
Use it when you want an assistant to work directly with mail and domain settings on JustEmails, such as reading or sending mail, adding domains, checking DNS or managing mailboxes. Best suited to teams already using JustEmails email hosting.
Requirements
A remote endpoint connection and a JustEmails account. Authentication is OAuth; clients without MCP sign-in must supply a JustEmails API key in the Authorization header.
Before you install
Requires JustEmails credentials: OAuth authorization or an API key in the Authorization header. The assistant can send mail, add domains and change mailbox settings, which modify real data, and sending mail reaches outside recipients. Check the scope you grant.

Installation

In SourceWeft

  1. Open JustEmails 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/app.justemails%2Fmcp/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": {
    "justemails": {
      "type": "http",
      "url": "https://mcp.justemails.app/mcp"
    }
  }
}

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

2
  1. v0.2.0LatestSep 30, 2026
  2. v0.1.0Sep 30, 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.