Productivity & Project Management · Craft MCP + Claude
Craft MCP with Claude: Search, Notes and Task Management Through Natural Language
The short answer
Claude connects to Craft through the Craft MCP server, a secure bridge that lets Claude search documents, read daily notes, create and update tasks, and manage collections. Access uses the DCR OAuth sign-in method, and people set the permissions and approve consequential changes before they happen.
What is Craft MCP?
Craft is a structured workspace service for documents, daily notes, tasks and collections. Teams use it to store, organise and share working content with rich structure and context attached. Project managers, operations staff, researchers, writers and knowledge teams often use it as a central place for meeting notes, plans and running to-do lists. Because the content is structured, it is well suited to being searched and updated by an AI assistant rather than read line by line.
How Claude connects to Craft MCP through MCP
MCP, the Model Context Protocol, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a tool. Once Craft is connected, Claude can work with your workspace in plain language, for example finding the document that holds last quarter's plan or listing open tasks for a named project.
Typically, Claude can search documents, read the content of daily notes, create new tasks, update existing ones and organise items within collections. The exact actions available depend on how the connection is configured. We set it up so Claude only reaches the spaces and content your team needs.
Permissions and approvals keep people in charge. Access is granted through DCR OAuth sign-in, which you control and can withdraw at any time. Actions are scoped to the least privilege needed, and important changes such as bulk edits or deletions can require a person to confirm first. Every interaction can be logged for review.
What you can automate
Finding documents in seconds
Staff can ask Claude to locate a proposal, policy or meeting record by topic, date or keyword. Instead of scrolling through folders, a project coordinator might ask for every document that mentions a client name from the past six months and receive a short summary with links back into the workspace.
Turning daily notes into action
Many teams jot down decisions and follow-ups in daily notes that then get lost. Claude can read the day's notes and propose tasks from them, such as an action for the operations lead or a reminder for the finance team. A person reviews the list before the tasks are created.
Keeping task lists current
Team leads can ask Claude to update task status, change due dates or reassign items after a stand-up. This saves time on administration and keeps the workspace accurate, which matters when several people depend on the same plan.
Organising collections for projects
Collections often grow untidy over time. Claude can help group related documents and tasks into the right collection for a project, reducing duplicate pages and making handovers smoother for new team members.
Preparing weekly summaries
A department head might ask Claude to gather the week's notes and open tasks into a short status summary for leadership. The summary draws on the workspace content directly, so it reflects what the team actually recorded rather than what someone remembers.
An end-to-end workflow: Weekly project status report
TriggerEvery Friday at mid-afternoon, the project manager asks Claude for the week's status update.
Claude searches Craft for daily notes and documents tagged to the active project from the past seven days.
Claude reads the notes and identifies decisions, blockers and completed actions.
Claude lists open and overdue tasks from the project collection in Craft.
Claude drafts a status summary and sends the draft into Microsoft 365 as a Word document for the project manager to review.
The project manager edits the draft, and any new follow-up tasks Claude proposes are approved before they are created in Craft.
The approved report is shared with the steering group through Microsoft 365.
OutcomeTypically, the report that once took half a day to compile is ready within an hour, and it is built from what the team actually recorded during the week. Leaders receive consistent updates and fewer missed follow-ups.
How we set it up
Free automation audit
We review how your team uses Craft today and identify the workflows worth automating, such as task capture, document search or weekly reporting. You leave with a clear list of priorities and no obligation to proceed.
Connect Craft through MCP
We connect Claude to Craft using the Craft MCP server and DCR OAuth sign-in, so each user authorises access with their own account. Permissions are set to the least privilege the workflows need.
Design and build the workflow
We design the end-to-end process across Craft and your other systems such as Microsoft 365, CRM or ticketing tools. People approve consequential actions, and we agree exactly where human review sits.
Test against real cases
We test the workflow using past projects and real daily notes from your workspace. We refine prompts, permissions and approval points until the output matches what your team expects.
Launch, monitor and train
We launch with audit logging and monitoring in place, then train your team on asking Claude for what they need and reviewing its suggestions. We check results after the first month and adjust as required.
Who benefits
- Project managers
- Faster status reports and fewer missed follow-ups, drawn directly from the notes the team records.
- Operations leads
- Cleaner task lists and quicker answers to questions about where things are recorded.
- Knowledge and documentation teams
- Easier retrieval of documents and better-organised collections across projects.
- Department heads and executives
- Consistent summaries of progress without waiting on manual compilation.
Security and control
- Access is granted through DCR OAuth sign-in, so each user connects with their own authorised account.
- Claude is given least-privilege access, limited to the spaces and actions each workflow needs.
- People approve consequential changes such as bulk edits, deletions or sharing content outside the team.
- Audit logs record what Claude searched, read and changed, supporting review and accountability.
- Sensitive notes can be excluded from the connection, and access can be withdrawn at any time.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to meet internal data handling policies. Indian organisations are supported in line with the Digital Personal Data Protection Act, 2023, with hosting in India where required. Companies in the UAE and Saudi Arabia are supported under their local data protection laws, with hosting chosen to match those requirements. Hosting location is selected during design so the setup suits your regulatory obligations.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Craft MCP server do?
The Craft MCP server is a secure bridge between Claude and your Craft workspace. It lets Claude search documents, read daily notes, create and update tasks and manage collections in response to plain-language requests. It only exposes the actions you allow, so the connection stays within boundaries your team sets.
Is connecting Craft to Claude secure?
Security depends on how the connection is set up. Access uses DCR OAuth sign-in, so each user authorises their own account, and permissions are limited to what each workflow needs. Important actions can require human approval, and audit logs record activity so you can review what happened.
What can Claude do with Craft once connected?
Typically, Claude can find documents by topic or date, summarise daily notes, draft and update tasks, and help organise content into collections. The exact range depends on the configuration we agree with you during design and the permissions you grant.
How long does setup take?
A focused setup for a single team often takes a few weeks, covering the audit, connection, workflow design, testing and training. Larger rollouts with several departments or additional systems take longer. We give you a clear timeline after the free automation audit.
Which plan or permissions are needed?
In general, you need a Craft workspace where you can authorise a connection and the permissions to access the content involved. The specifics depend on your workspace setup and organisation policies, so we confirm the requirements during the audit before any work begins.