Project Hub MCP terms of service
Project Hub MCP is my personal, locally run desktop pilot for keeping project sessions connected to their sources. These terms describe its intended use and practical limits. This website explains the tool; it does not provide an online account or Google sign-in.
Who may use it and for what
Project Hub is maintained for my own use and for people I explicitly authorize to participate in the pilot. Publication of this page does not grant access to the MCP, its code, a Google account, or project data.
Authorized use is limited to registered pilot projects through a configured desktop MCP client. Use it to find project context, review source-backed next actions, register confirmed sessions, and record evidence-based checkpoints. Provide accurate project IDs, session details, summaries, and evidence links. Do not use it to access projects or data you are not authorized to use, or to bypass the configured pilot restrictions.
How the pilot works
The MCP runs on a local computer through configured desktop clients, currently Codex and Claude Code. It reads designated Google Drive documents and a local routing policy, reads a fixed pilot Google Sheet, and writes confirmed session, checkpoint, and conflict records to that Sheet. The Sheets permission granted by Google can cover spreadsheets in the authorized account, although the current code directs its Sheets requests to the fixed pilot spreadsheet. The privacy policy explains permissions, data flow, storage, and retention in more detail.
Project Hub returns selected project information to the desktop client that called it. That client may keep the information in its own conversation or records under its own settings and terms. A checkpoint evidence URL is supplied by the caller; Project Hub does not inspect the linked content. Review returned context and any proposed changes before relying on them.
Availability and changes
This is a small pilot, not a continuously available service. It depends on the local computer and client configuration, Google authorization and APIs, the pilot Sheet, and designated source files. Access or features may be changed, paused, or discontinued. Records already written to the Sheet do not disappear automatically if the pilot stops.
Limitations
Project Hub may return incomplete or outdated context if a source is unavailable, has changed, or has not been reconciled. It does not independently verify caller-supplied evidence links. Its local lock coordinates its own writers, but other writers to the same Sheet can still conflict with an append. Check important source documents and Sheet records directly before making consequential decisions.
The pilot is provided as available, without a promise of uninterrupted operation, error-free results, or a particular outcome. These terms do not claim security measures or legal guarantees beyond what the current implementation supports.
Stopping use and access
To stop using Project Hub, remove it from the configured desktop client and stop running the local MCP. To end its Google access, revoke Project Hub in your Google Account’s third-party connections and delete the local OAuth token file described in the privacy policy. Reauthorizing it later would restore access.
Revoking access does not remove existing pilot Sheet rows or information already returned to a desktop client. Delete Sheet records manually if appropriate, and use the client’s own controls for its records. For questions or help with deletion, email [email protected].