feat(mcp): add Screenpipe to the built-in catalog - #201
Merged
kannandreams merged 3 commits intoOct 2, 2026
Merged
Conversation
kannandreams
force-pushed
the
feat/add-screenpipe-mcp
branch
from
October 2, 2026 21:29
27706ff to
1ee7508
Compare
Owner
|
Thanks for adding Screenpipe, and for disclosing that you maintain it. I checked the entry against the screenpipe-mcp README: the I pushed two changes to your branch:
@louis030195 |
kannandreams
added a commit
that referenced
this pull request
Oct 2, 2026
States when a server is added to the built-in catalog, so vendor pull requests like #201 get a consistent answer, and lists the files and checks an entry needs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Screenpipe to the built-in MCP catalog so
tuff add mcp screenpipecan configure access to locally captured screen text, audio and meeting history. The entry uses the official documentednpx -y screenpipe-mcp@latestcommand and forwardsSCREENPIPE_LOCAL_API_KEYas an environment reference.The description explains that Screenpipe must already be running on localhost:3030, where to obtain the key, and that configured cloud features can send context off-device. Screenpipe is source-available under the Screenpipe Commercial License. Current plans are linked rather than copied into the catalog. Includes an Unreleased changelog entry; the catalog website is generated from the TOML.
Sources: official MCP setup and tool documentation, license, product and plans.
Validation:
cargo +stable test -p tuff-core catalog::tests --locked(6 passed).cargo +stable test -p tuffcli mcp_catalog --locked(3 passed).npm --prefix website run build(49 pages built).git diff --check.tuff init, thentuff add mcp screenpipe -a open-agents -y; verified the generated MCP configuration contains the package command and an environment reference for the key.These checks validate the catalog and generated website. They do not run Screenpipe or query recordings. Used Rust 1.98.1 and Node 24.20.0 locally.
Disclosure: I maintain Screenpipe. This contribution was prepared with Codex.