Bench47
cloud.markbasePublished by markbase.cloudOfficial publisherv1.0.1Updated Nov 4, 2026
Shared Markdown memory for your agents: docs, typed collections, files, skills and Dispatch.
Overview
Remote MCP server providing shared Markdown memory for agents, covering docs, typed collections, files, skills and Dispatch.
- What you can do
- Store and share Markdown-based memory that multiple agents can read and reuse.
- Organize content as docs and typed collections.
- Manage files and skills alongside that memory.
- Use Dispatch, a feature named in the description whose details are not documented here.
- No tool list is published, so exact operations are unknown.
- When to use it
- When several agents or assistants need a common, persistent Markdown knowledge store rather than per-session context, and you are willing to connect to a hosted service with OAuth sign-in.
- Requirements
- A remote streamable HTTP endpoint at api.markbase.cloud; no local package or runtime. OAuth authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Bench47 in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/cloud.markbase%2Fmarkbase/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.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.markbase.cloud/mcp"
}
}
}Tools
0Version history
2- v1.0.1LatestNov 4, 2026
- v1.0.0Oct 29, 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.
