AcornReply

com.acornreplyPublished by acornreply.comOfficial publisherv1.3.0Updated Oct 26, 2026

Set up AcornReply workspaces and read and edit your knowledge base.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

AcornReply is a remote MCP server that lets an assistant set up workspaces and read and edit your knowledge base.

What you can do
  • Set up and configure AcornReply workspaces
  • Read content from your knowledge base
  • Edit knowledge base content
  • Authenticate with OAuth sign-in or a workspace API key
When to use it
Useful when you want an assistant to help organize an AcornReply workspace or to look up and update entries in your knowledge base without switching tools.
Requirements
A remote MCP endpoint at mcp.acornreply.com over streamable HTTP. Authentication is required: OAuth sign-in for clients that support it, or an Authorization header carrying a workspace API key. An AcornReply account and workspace are implied.
Before you install
The server can edit your knowledge base, so changes made by the assistant may alter or overwrite existing content. The Authorization header carries a workspace API key; treat it as a secret and prefer OAuth where available. Your knowledge base content is sent to the remote service.

Installation

In SourceWeft

  1. Open AcornReply 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.acornreply%2Fserver/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": {
    "acornreply": {
      "type": "http",
      "url": "https://mcp.acornreply.com/"
    }
  }
}

README

This repository has no README.

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. v1.3.0LatestOct 18, 2026
  2. v1.0.1Sep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.