What tools connect an agency's AI tools to client context?
There are 3 ways. Copy 1 client context file into each tool's project. Store the file in shared drives that each tool can read. Or use MCP connectors so assistants read the source directly. All 3 need 1 master file per client that a person owns.
Option 1: copy into projects. Claude Projects, ChatGPT projects and Gemini Gems each hold files. Simple. The risk is copies drifting apart.
Option 2: shared drive. Keep the master file in Google Drive and connect it to each tool. Better. Still depends on each tool's connector.
Option 3: MCP connectors. Assistants read the source directly through a connector. Best for teams with many clients and many tools. Start read-only.
The rule for all 3. 1 master file per client. 1 named owner. Every fix to a draft becomes a line in that file.
Why it matters. When AGL mapped 1 internal team, 80% of activity involved sharing information and context.
FAQ
- Which option should a small agency start with?
- Option 1 is fine under 10 clients if 1 person owns the master file.
- When do MCP connectors make sense?
- When the team uses several AI tools across many clients and copies keep drifting.
- What goes in the master file?
- Goals, voice, no-go rules, approved proof, contacts, approvers and history.