Hedwig

com.hedwig-aiPublished by hedwig-ai.comOfficial publisherv1.0.0Updated Oct 24, 2026

Read, arrange, and build agents on your Hedwig email board from any AI client. Nothing ever sends.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant read and arrange agents on a Hedwig email board, with nothing ever being sent.

What you can do
Hedwig exposes an email board to an AI client so the assistant can read what is on the board, arrange items, and build agents there. The description states that nothing ever sends, so the server is presented as a read-and-organize surface rather than a mail-sending tool. No individual tools are listed in the manifest.
When to use it
Worth adding when you already use Hedwig and want an AI client to work with your email board: reviewing what is there, organizing it, and setting up agents. It is not intended for sending mail, since the description says nothing ever sends.
Requirements
A remote streamable HTTP endpoint at the provider's site; no local package or runtime is declared. Authentication is OAuth and is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth, so review the scopes and permissions requested during sign-in before authorizing. The description says nothing ever sends, but the board content is still read by the assistant and handled by the remote provider, so consider what email data is exposed to it.

Installation

In SourceWeft

  1. Open Hedwig 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.hedwig-ai%2Fhedwig/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": {
    "hedwig": {
      "type": "http",
      "url": "https://www.hedwig-ai.com/api/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. v1.0.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

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