
Recolx MCP
io.github.uzqwPublished by GitHub account uzqwv0.1.0Updated Oct 24, 2026
Read-only access to your Recolx recordings, transcripts and templates (stdio)
Overview
Gives an assistant read-only access to your Recolx recordings, transcripts and templates through a local stdio server.
- What you can do
- This MCP server connects an assistant to a Recolx account so it can read your recordings, transcripts and templates. It runs as a local process over stdio and is described as read-only, so it is meant for retrieving and working with existing content rather than changing it. The manifest lists no tools, so the exact operations are not documented here.
- When to use it
- Worth adding when you keep meeting or voice recordings in Recolx and want an assistant to search, summarize or quote from the transcripts and templates without exporting files by hand. It is a desktop-only local server, so it suits a single machine rather than a shared or web deployment.
- Requirements
- A local runtime able to run the npm package @uzqw/mcp over stdio, on a desktop machine. The manifest declares no authentication, environment variables or headers, but access to your Recolx recordings implies some form of Recolx account or local data the server reads.
Installation
In SourceWeft
- Open Recolx MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.