
Recall
io.github.imjakezimmer32Published by GitHub account imjakezimmer32v1.0.1Updated Oct 24, 2026
Notes, files, GitHub, and Drive through one MCP connection.
Overview
Connects an assistant to notes, files, GitHub and Drive through one MCP endpoint.
- What you can do
- Recall is a remote MCP server that presents notes, files, GitHub and Drive through a single connection. The registry description summarizes it as notes, files, GitHub, and Drive through one MCP connection. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Worth considering when an assistant needs to reach several personal or team sources, such as notes, files, GitHub and Drive, without setting up a separate server for each. It suits users who already have an account on the provider's site and can mint a bearer token there. It is less useful if you only need one of those sources or want documented per-tool behavior before installing.
- Requirements
- A remote MCP endpoint at over streamable HTTP. Authentication is required: a bearer token supplied in the Authorization header, described as minted on Me and shown once. No packages or environment variables are declared. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Recall in the dashboard and add it to a workspace.
- Connect Authorization token 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/io.github.imjakezimmer32%2Frecall/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.
{
"mcpServers": {
"recall": {
"type": "http",
"url": "https://recall.arraybud.app/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 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.