The idea in one paragraph
An MCP server exposes a capability (read my calendar, query my database, post to my CMS) in a form any MCP-aware tool — Claude Code among them — can call. Your workspace's AI Instructions then reference those capabilities: "weekly updates pull events from the calendar server, then summarise Meetings/". Structure plus reach.
A first, useful workflow
Start with one server and one recurring task. A good first candidate for any workspace:
- Add a filesystem or calendar MCP server to your Claude Code config.
- Note it in AI Instructions/claude.md: what the server does and when to use it.
- Automate one weekly artefact — a status note, a content plan, a revision schedule.
TRY THIS PROMPT
Using the calendar MCP server, list next week's commitments, then draft a weekly plan into Meetings/ following this workspace's template.
Keep the workspace authoritative
MCP results are inputs; the workspace is the record. Have the AI write outcomes back into the folders so every session still starts from files, not from memory of past sessions.