Email-Ops

ai.unicorncommanderPublished by unicorncommander.aiOfficial publisherv0.1.0Updated Nov 7, 2026

Mailbox threads; drafts wait for a person. Authenticated; OAuth 2.1 via Keycloak.

The publisher's own server: Accounting-Ops

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote email operations server that lets an assistant work with mailbox threads and prepare drafts that wait for a person to review.

What you can do
  • Work with mailbox threads, as described in the registry entry.
  • Prepare drafts that are held for a person to review rather than sent automatically.
  • Connect over a remote streamable HTTP endpoint with OAuth 2.1 authentication.
  • No individual tools are listed, so the exact operations are not documented.
When to use it
When you want an assistant to help triage or follow email conversations and stage replies as drafts for human approval, without giving it unattended sending.
Requirements
A remote endpoint at email-ops.unicorncommander.ai over streamable HTTP. OAuth 2.1 authentication through Keycloak is required; no environment variables or headers are declared.
Before you install
It handles mailbox content, which is private data, and that content is processed by a third-party service. Access is granted through OAuth, so review the scopes requested. The description says drafts wait for a person, but confirm that no tool can send mail before relying on that.

Installation

In SourceWeft

  1. Open Email-Ops 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/ai.unicorncommander%2Femail-ops/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": {
    "email-ops": {
      "type": "http",
      "url": "https://email-ops.unicorncommander.ai/api/v1/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

1
  1. v0.1.0LatestNov 7, 2026

Score

83% 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
  • 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.

Other Unicorncommander integrations