Bench47

com.bench47Published by bench47.comOfficial publisherv1.0.0Updated Nov 5, 2026

Shared Markdown memory for your agents: docs, typed collections, files, skills and Dispatch.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Bench47 is a remote MCP server giving agents shared Markdown memory: docs, typed collections, files, skills and Dispatch.

What you can do
  • Store and share Markdown documents as memory that multiple agents can read.
  • Organize content into typed collections.
  • Work with files alongside the Markdown docs.
  • Use skills and a feature called Dispatch, per the provider's description.
  • No tool list is published, so exact operations are not documented here.
When to use it
When several agents or sessions should share a common, persistent Markdown knowledge base instead of each keeping its own context. Useful if you want docs, collections and files kept in one hosted place that assistants can reach over the network.
Requirements
A remote MCP endpoint at the provider's API host, reached over streamable HTTP. OAuth authentication is required, so a Bench47 account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
Content you store is held by a third-party hosted service, so anything written there leaves your machine. OAuth grants access to your Bench47 account. The tool list is not published, so what the server can read, write or delete is unverified before connecting.

Installation

In SourceWeft

  1. Open Bench47 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.bench47%2Fbench47/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": {
    "bench47": {
      "type": "http",
      "url": "https://api.bench47.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.0LatestNov 5, 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.