Repository navigation
Correct Screenpipe MCP access, authentication and cloud context - #111
louis030195 wants to merge 4 commits into
Conversation
|
Someone is attempting to deploy a commit to the assafbar-gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Resolved the changelog conflict against current main in Could you review this correction for the next weekly drop? GitHub Actions approval and Vercel preview authorization remain on the maintainer side. |
|
Thanks: MCP access is live at https://agentswitchboard.dev/agents/screenpipe, in the November 10, 2026 drop. The rest of the listing stays as it is. Pull request #370 carries the change and credits this one, so this pull request is closed rather than merged. |
What kind of change?
The Screenpipe entry omits MCP access, says authentication is unnecessary, and describes capture as never sending data to a server. This updates the existing listing to point to the official MCP setup, identify local API key authentication, and distinguish local capture from configured cloud services.
The description and skills now focus on searchable history, recall and work summaries. Additional context documents the source-available Screenpipe Commercial License and links current pricing. I replaced the unsourced cohort and broad privacy tags with specific capability tags. The existing maintainer-set featured and directory tier fields are preserved; verified is set to false for this vendor correction as requested by CONTRIBUTING.md.
Relationship: I am Screenpipe's founder/maintainer, submitting on behalf of the product.
Sources checked:
Checklist
npx tsx scripts/validate-content.tspasses locally: 690 agents, 22 categories, zero violationscontent/changelog.jsonverified: falsefor maintainer reviewgit diff --checkalso passes. Only the listing JSON and changelog changed. I have not claimed a new live endpoint verification; the existing recorder and configured local key are required for the MCP workflow.Updated against upstream main on October 7, 2026 and resolved the changelog conflict, preserving all 810 upstream entries and the Screenpipe correction. The content validator and whitespace check pass. The Vercel preview still requires authorization from the upstream project owner.