Replyhand

com.replyhandPublished by replyhand.comOfficial publisherv1.0.0Updated Oct 24, 2026

Run your Replyhand inbox, contacts, AI agent and reports from your own AI assistant.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant operate a Replyhand inbox, contacts, AI agent, and reports from within the assistant.

What you can do
The description states it runs your Replyhand inbox, contacts, AI agent and reports from your own AI assistant. No individual tools are listed in the manifest or registry entry, so the exact operations are not documented in the supplied material.
When to use it
Consider it when you already use Replyhand and want your AI assistant to work with that inbox, contact list, AI agent, and reports instead of switching to the Replyhand interface. Because no tool list is published, it is hard to judge fit for other cases.
Requirements
A remote MCP endpoint at using streamable HTTP. OAuth authentication is required. No environment variables, headers, or packages are declared. A Replyhand account is presumably needed, though the input does not state this explicitly.
Before you install
The registry description is the only source of detail; no tool list, README, or permission scope is published, so what the assistant can read, send, or change in the inbox, contacts, and reports is not documented here. Authentication is OAuth, so review the consent screen and granted scopes before connecting.

Installation

In SourceWeft

  1. Open Replyhand 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.replyhand%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": {
    "replyhand": {
      "type": "http",
      "url": "https://replyhand.com/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.0LatestOct 9, 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.