Correct Screenpipe MCP access, authentication and cloud context - #111
Open
louis030195 wants to merge 1 commit into
Open
louis030195 wants to merge 1 commit into
louis030195 wants to merge 1 commit 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.
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
1 participant
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.
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: 573 agents, 21 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.