How to Connect Claude to Your SOP Library Using MCP

The Gap Between Claude and Your Actual Processes

If you’ve been using Claude to help with work, you’ve probably run into the same wall: Claude gives you a smart general answer, but it doesn’t know your answer. It doesn’t know that your company’s client onboarding takes seven steps and the third one is always where things go sideways. It doesn’t know that your invoice approval process changed in January. It doesn’t know what “the standard way we handle this” actually means for your team.

That gap isn’t Claude’s fault. It’s an architecture problem. Claude is a general-purpose AI. Your SOPs live somewhere else — a process library, a shared drive, a wiki. Until recently, those two things had no reliable way to talk to each other.

The Model Context Protocol (MCP) is what closes that gap.

What MCP Actually Is

MCP is an open protocol — released by Anthropic in late 2024 — that lets AI assistants connect directly to external tools and data sources. Instead of pasting process documents into a chat window, you configure Claude once and it can query your process library like it would any other tool.

The practical difference: Claude stops giving you generic best-practice answers and starts giving you answers grounded in your processes.

From Anthropic’s documentation, MCP works the same way across local clients like Claude Desktop and agentic environments like Claude Code. You configure a server, give it a key, and Claude’s toolset expands to include everything that server exposes.

What’s the Process For’s MCP Server

We built an MCP server for What’s the Process For. It’s an npm package (@whatstheprocessfor/mcp) that installs in three steps and connects Claude to your process library with read, write, and publish permissions scoped to your API key.

Once it’s connected, Claude has access to seven tools:

• list_processes — page through your library, filter by title or visibility
• get_process — fetch any single process with its full step list
• create_process — draft a new process from scratch (validates URLs and plan limits automatically)
• update_process — edit any field on an existing process; prior version is snapshotted automatically
• publish_process — mark a process live, change visibility in the same call
• delete_process — permanently remove a process (requires a key with the processes:delete scope)
• whoami — confirm the key is working and which user or org it acts as

The server runs with the same permissions as your login, nothing more. A personal API key reaches only your personal processes; if you want Claude to touch org-level processes, you mint an org key at the organization settings page.

Full setup instructions are at /developers/mcp.

What This Looks Like in Practice

Abstract protocol descriptions are not useful. Here are three concrete situations where this changes how a small team operates.

Situation 1: Claude surfaces the right SOP mid-task

Your office manager is handling a client escalation. She opens Claude, describes the situation, and asks: “What’s our process for handling a billing dispute?” With MCP connected, Claude calls list_processes, finds the billing dispute SOP, pulls the steps via get_process, and returns the actual process — not a generic answer about how companies handle billing disputes in general.

This isn’t a chatbot that has vaguely read your documentation. It’s Claude with live access to your current version of that specific process.

Situation 2: Claude drafts a new SOP and saves it to your library

Your operations lead is documenting a new vendor onboarding flow. She describes the steps to Claude in plain language. Claude uses create_process to structure it, validate the format, and save it as a draft directly into the process library. The whole thing takes five minutes instead of forty-five.

She still reviews it. That’s the right workflow — Claude does the drafting and structural work, a human confirms it’s right before publishing.

Situation 3: Claude updates a process that changed

Your team switched CRMs. Fifteen of your processes reference the old CRM. Instead of hunting through each one manually, your Claude-connected workflow can call get_process on each affected SOP, identify the outdated references, use update_process to revise them, and log what changed. The previous version is automatically snapshotted, so nothing is irreversibly overwritten.

This is the kind of work that silently doesn’t get done at most small companies — and outdated SOPs are worse than no SOPs, because they generate false confidence.

Who This Is (and Isn’t) For

This is useful if you have:

• An existing process library in What’s the Process For with 10+ documented processes
• A team that’s already using Claude Desktop or Claude Code in their day-to-day work
• At least one person who’s comfortable doing a one-time config setup (it takes about ten minutes)

This is not useful if:

• You haven’t documented your processes yet — MCP doesn’t help Claude invent SOPs from thin air, it helps Claude work with the ones you’ve already written
• You’re looking for automated, no-human-in-the-loop SOP management — human review before publish is the correct approach, not an optional nicety
• You’re on a team that isn’t using Claude at all — the REST API at /developers/api is the right starting point if you want to build integrations with other AI tools or systems

The Competitive Reality Right Now

As of April 2026, no other SOP platform — not Trainual, not Process Street, not Notion, not Scribe — has a native MCP server. That’s not a permanent advantage; they’ll build one eventually. But it does mean that if you’re already using Claude and you want your AI to work with your actual documented processes, the only way to get that today is through What’s the Process For.

We’re not saying that to be promotional. We’re saying it because if you’re reading this trying to decide whether to evaluate MCP-connected SOP management, the honest answer is that we’re the only production option right now.

More detail on what we support for AI agents and automation is at /for-agents.

Why This Matters More Than the AI Hype Cycle Usually Delivers

Most “AI + SOPs” content is about using AI to generate SOPs from scratch. That’s useful, but it’s a one-time productivity gain during authoring. MCP is different — it’s about AI having continuous, live access to your process library as part of ongoing work.

The value compounds over time because it inverts the friction model. Without MCP, employees have to remember to look up a process (they often don’t), find the right version (also uncertain), and reference it mid-task (rare once they’re already moving). With MCP, the AI they’re already talking to can pull the right process at the right moment — without the human having to think to ask.

That’s not AI replacing process management. That’s AI making the process management you’ve already done actually accessible at the point of need. (Per StoryBrand: the team is the hero, the tool is the guide that hands them the right information — Claude plus your process library, not either one alone.)

Setup Takes About Ten Minutes

If you want to try this:

1. Log in to What’s the Process For (or start a free trial — no credit card required).
2. Go to your account settings and mint an API key.
3. Follow the setup guide at /developers/mcp — it’s three config steps for Claude Desktop, one terminal command for Claude Code.
4. In Claude, ask: “Run the whoami tool from whatstheprocessfor.” You should see your user ID come back. That confirms it’s working.
5. Then: “List my processes.” You’ll see your library.

From there, what you do with it depends on your workflow. Most people start by asking Claude to surface specific processes during real work, then move to having Claude help draft new ones.

Related Reading

• Best SOP Software 2026 — where What’s the Process For fits in the broader landscape
• How to Write a Business Process — getting your processes into good shape before connecting them to Claude
• MCP Setup Guide — the technical setup reference
• REST API Reference — for non-Claude integrations

---

The process library you’ve built is only useful if your team can access it at the right moment. Connect Claude via MCP and see whether your existing SOPs actually surface when you need them.