
ProjectKeeper
io.github.feiyanglyy-stackPublished by GitHub account feiyanglyy-stackv1.0.0Updated Oct 24, 2026
What a project planned, decided and did, for your agents: context packs, notes and the table check.
Overview
ProjectKeeper gives an assistant access to a project's recorded plans, decisions and activity through context packs, notes and a table check.
- What you can do
- According to its registry description, ProjectKeeper supplies agents with what a project planned, decided and did. It exposes this as context packs, notes and a table check, so an assistant can pull project context rather than relying only on the current conversation. No tool list is published, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant needs background on a project's plans and past decisions before answering or acting. It suits local, desktop-based workflows where project context should be available to the agent.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the npm package projectkeeper and started with npx, so Node.js and network access for package retrieval are needed. It is desktop only, with no web executable. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open ProjectKeeper 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- v1.0.0LatestOct 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.