[FEATURE] API / sync mechanism for Claude Team Project knowledge files

Problem

I run a startup where Claude is deeply integrated into our operating system — Claude Code on the CLI, claude.ai for research and document creation, and a Claude Team Project as a shared knowledge base for my team.

The Team Project knowledge base has no programmatic update mechanism. Files must be manually uploaded through the web UI. This creates a real operational gap:

• My source of truth is a git repo that auto-syncs to Google Drive
• Claude Code updates these files throughout the day (competitive intel, investor pipeline, decisions log, etc.)
• My team members access the shared knowledge through the Claude Team Project
• Every time a file changes, someone has to manually re-upload it to the Team Project
• In practice, this means the Team Project is perpetually stale

I've built workarounds (sync protocols, migration docs, manual upload checklists) but they're brittle and add friction to what should be a seamless workflow.

Proposed solution

Any of these would unblock the workflow:

1. Project Knowledge API — CRUD endpoints for project knowledge files, so I can script uploads from CI or a post-commit hook
2. Google Drive / cloud storage sync — Point a Team Project at a Drive folder (or S3 bucket, or git repo) and keep knowledge files in sync automatically
3. MCP tool for project knowledge — Let Claude Code push updated files to a Team Project directly

Why this matters

Claude Team is positioned as the collaboration layer, but without dynamic knowledge updates, it's a snapshot in time rather than a living workspace. For teams that treat Claude as an always-on operational tool (not just a chat interface), the static upload model is the single biggest friction point.