Craft MCP
Craft MCP lets agents search, read, create, update, and delete authorized Craft documents, daily notes, tasks, collections, and structured workspace content.
Verdict
Common use cases
- Search meeting notes during project planning
- Pull product specs into design reviews
- Reference onboarding docs for new hires
- Find decision records from past sprints
- Retrieve client briefs mid-conversation
Integration
- Vendor
- Craft MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
craft_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Craft MCP in the list and click Connect. 3. You'll be redirected to Craft's OAuth authorization screen — sign in with your Craft account if prompted. 4. Review the permissions request (typically read access to documents and spaces) and click Authorize. 5. Switchy will confirm the connection and redirect you back to the integrations page. 6. Open any Project in your workspace and type '@Craft' in the chat to invoke the integration. 7. Test it by asking the AI to search for a document title you know exists in your Craft workspace — if it returns results, the connection is live.
What teammates see: by default, memories from Craft MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Find Recent Notes
@Craft search for all documents modified in the past 7 days and summarize the key topics covered in each.
Retrieve Project Brief
@Craft find the document titled 'Q1 Product Roadmap' and extract the main deliverables and deadlines.
Summarize Meeting Notes
@Craft get the notes from yesterday's standup meeting and list all action items assigned to team members.
Compare Two Documents
@Craft retrieve 'Design Spec v1' and 'Design Spec v2' then compare them and tell me what changed between versions.
Search by Keyword
@Craft search all documents for mentions of 'API authentication' and show me the relevant sections with context.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@craft search for all documents tagged 'Q1 planning' and show me the most recent three with their last update dates
Here are the three most recent documents tagged 'Q1 planning': 1. **Q1 Revenue Targets** — Last updated Jan 15, 2024 by Sarah Chen. Contains financial projections and department breakdowns. 2. **Marketing Campaign Timeline** — Last updated Jan 12, 2024 by Mike Torres. Outlines campaign phases through March. 3. **Product Roadmap Draft** — Last updated Jan 8, 2024 by Alex Kim. Feature prioritization for Q1 release cycle. This example shows how the MCP would return document metadata from your Craft workspace based on tag filters.
This read operation requires OAuth scope for document access. Results depend on your team's Craft organization structure and tagging conventions. The MCP returns metadata and summaries, not full document content, so follow-up prompts may be needed to drill into specifics.
@craft create a new document titled 'Sprint 12 Retrospective' in the Engineering folder with sections for What Went Well, What Needs Improvement, and Action Items
Created document **Sprint 12 Retrospective** in the Engineering folder. The document includes three sections as requested: - What Went Well - What Needs Improvement - Action Items Each section is formatted as a heading with placeholder text prompting team input. The document is now accessible to all members with Engineering folder permissions. This example illustrates how the MCP handles document creation with structured templates.
This write operation creates a real document in your Craft workspace. Verify folder permissions before running — the MCP inherits your OAuth user's access level. If the specified folder doesn't exist or you lack write permissions, the operation will fail with an error message.
@craft pull the last five meeting notes from the Leadership folder and draft a summary of recurring themes around hiring challenges
Analyzing the last five Leadership meeting notes, three recurring themes emerge around hiring: **Pipeline Volume**: Four of five meetings mention difficulty sourcing senior engineering candidates, particularly for backend roles. The Dec 18 note flags a 40% drop in qualified applicants. **Interview Cycle Length**: Three meetings discuss extending timelines (now averaging 6 weeks). The Jan 5 note proposes adding a technical assessment earlier in the funnel. **Compensation Benchmarking**: Two meetings reference competitor salary data, with consensus that current ranges lag market by 10-15% for L5+ roles. This synthesis combines document retrieval with AI analysis to surface patterns your team is tracking.
This example pairs the MCP's document access with the AI's reasoning capability. Accuracy depends on how consistently your team structures meeting notes. The MCP fetches content, but the AI interprets themes — review the source documents to verify the summary aligns with your team's actual discussions.
Use-case deep-dives
Craft MCP bridges the spec-to-code gap
A 6-person product team ships features every two weeks. Designers draft specs in Craft, engineers pull them into Linear tickets, and the handoff gets messy—screenshots go stale, context gets lost in Slack threads. Craft MCP is the right call here if your team already lives in Craft for documentation. OAuth2 auth means each engineer connects their own account, so the AI can fetch the latest spec version during standup or code review without manual copy-paste. The trade-off: if your specs are mostly in Notion or Google Docs, adding Craft just for MCP access doesn't pay off. But if Craft is already your single source of truth, this integration turns your AI workspace into a live link to the latest design decisions.
Onboarding new hires with company knowledge
A 12-person startup hires two engineers in Q1. The onboarding runbook, architecture decisions, and team norms all live in Craft. Without MCP, new hires ping the team lead every hour with questions that are already documented. With Craft MCP, the AI workspace becomes the first stop—new hires ask "how do we handle feature flags" and get the answer pulled from the canonical Craft page, not a stale wiki or a busy coworker's memory. This works if your Craft docs are up to date and well-organized. If your knowledge base is scattered across three tools or hasn't been touched in six months, the MCP will surface outdated answers and slow onboarding down. Keep Craft current, and this integration cuts onboarding questions by half.
Client project status updates for agencies
A 4-person agency juggles eight client projects. Each client gets a weekly update email summarizing progress, blockers, and next steps. The project manager drafts these updates in Craft, but pulling the right details from each project doc takes 20 minutes per client. Craft MCP changes the math: the AI workspace queries the latest project notes, extracts the key points, and drafts the update in two minutes. OAuth2 means each team member connects their own Craft account, so the AI only sees projects they have access to. The boundary: if your updates need data from tools outside Craft—like time tracking or invoices—you'll still need manual assembly. But for teams that document everything in Craft first, this integration turns status updates from a Friday afternoon slog into a five-minute task.
Frequently asked
What does the Craft MCP do in Switchy?
The Craft MCP connects your Craft documents and notes to Switchy's AI workspace. Your team can query document content, search across spaces, and reference Craft pages directly in AI conversations without switching apps. Since Craft organises knowledge hierarchically, the MCP preserves that structure when pulling context into Switchy threads.
What OAuth permissions does Craft MCP request?
Craft MCP uses OAuth2 to authenticate, requesting read access to your documents and spaces. The exact scope list depends on Craft's API implementation, but typically includes viewing document content and metadata. You'll see the full permission list during the OAuth flow — review it before authorising to confirm it matches your team's access policies.
Can the Craft MCP create or edit documents?
That depends on which tools the MCP exposes and what scopes you grant during OAuth. Most read-focused MCPs start with view-only access. If your use case requires writing back to Craft — creating pages, updating blocks — check the MCP's tool list in Switchy's directory once it's fully documented, or test it in a sandbox space first.
Why use Craft MCP instead of copying text into Switchy manually?
Manual copying breaks when documents update. The MCP pulls live content, so your AI context stays current as your team edits Craft pages. It also preserves links between documents and respects Craft's permission model — you only surface content the authenticated user can already see. For one-off questions, copy-paste works fine. For ongoing work, the MCP saves time.
Who on the team should connect the Craft MCP?
Anyone with a Craft account can connect it via OAuth. The MCP will only access documents that user can see, so connect it with an account that has visibility into the spaces your team needs. If you're centralising integrations, use a service account or team admin login to maximise coverage across shared Craft content.