DocDigest

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Corporate email and chat thread summarization parser.

VerifiedSSEWeb executableCommunication & Collaboration

Overview

AI-generated overview

DocDigest is a remote MCP endpoint that summarizes corporate email and chat threads, with a paid premium settlement option.

What you can do
Summarize corporate email and chat threads into condensed digests, based on the registry description. The server is a remote endpoint reached over SSE; no individual tools are listed in the manifest. Premium settlement is handled through a payment signature header rather than a conventional API key.
When to use it
Worth considering when an assistant needs to condense long corporate email or chat threads into short summaries, and you are comfortable with a hosted third-party endpoint.
Requirements
A remote SSE endpoint at the provider's hosted address; no local runtime or package is needed. Premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. No other accounts, keys or environment variables are declared.
Before you install
The server asks for a payment-signature header, which is a cryptographic authorization to transfer funds; treat it as a spending credential and only supply it if you accept the payment terms. Email and chat content sent for summarization goes to a third-party hosted service, so consider confidentiality before use. No tools are listed, so the exact data handling cannot be verified from the manifest.

Installation

In SourceWeft

  1. Open DocDigest in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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/io.github.Evozim%2Fdocdigest/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.

{
  "mcpServers": {
    "docdigest": {
      "type": "sse",
      "url": "https://docdigest-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 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 listedRequired15 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.