Skip to main content
The Kowalah MCP Server (also known as the Kowalah Claude Connector) lets you talk to your Kowalah workspace from inside Claude. It connects via OAuth using your Kowalah account and respects the same role-based permissions as the platform.

​
What you can do

The connector covers four jobs, across twelve tools:

Get an update

Ask Claude how things are going. Get a portfolio rollup, a focused view of a project, deliverable, Expert Request, or opportunity, and see any discovery invites waiting for your input.

Find an accelerator

Search the global Kowalah library and your organization’s private accelerators for a prompt, GPT, or workflow that already solves your problem.

Raise an opportunity

Capture a new idea, ask, or question for Kowalah to triage. Optionally link it to a discovery you’ve been invited to.

Check your training

What you’re booked on, your agenda for the day, and your own results, scores, badges, and certificates.

Read your operating model

Your coverage map, a function’s process portfolio, or one process in full: steps, dispositions, quality evals, and the work already aimed at it.

Keep the map true

Edit the processes and steps you own, set targets and quality bars, and propose changes to the ones you don’t.

​
Work your operating model in conversation

The AI Operating Model tools are the biggest thing the connector does beyond reporting status. Ask Claude where AI could help most, drill into a function, talk a single process through step by step, then fix what’s wrong:
If the process is yours, or sits below you in the org tree, the change lands. If it isn’t, Claude offers to propose it to the owner instead, and knows which of those applies before it tries.

Your operating model in Claude

The full walkthrough: reading the map, setting targets and evals, and proposing changes

​
Find the discoveries you’re invited to

When Kowalah runs a Discovery, each person on the audience gets a brief asking for their experience of a specific problem. The connector surfaces those briefs to you the moment you ask Claude for an update. Ask Claude:
Claude calls kowalah_get_update and the response includes a pending_discoveries section listing each discovery you’ve been invited to, along with:
  • The discovery’s goal — what Kowalah is researching
  • The business value context — why it matters
  • The close date — when responses are no longer being collected
  • The project the discovery sits against (if any)
You only see the brief that’s been shared with you; you don’t see other people’s responses or the discovery’s internal triage.

​
Submit an opportunity

Anyone in your organization can raise an Opportunity through the connector — admin, core team, or member. The customer doesn’t decide upfront whether the work is a deliverable, an Expert Request, or a new project; Kowalah’s team triages it after submission. Ask Claude:
Claude will:
  1. Check the accelerator library first — there may already be a prompt or workflow that solves it
  2. Walk you through goal, what good looks like, and context Kowalah needs
  3. Call kowalah_create_opportunity with a properly-fleshed-out description
  4. Show you the opportunity number (OPP-XXXX) so you can refer back to it
You can also pick Submit an opportunity from Claude’s prompt menu. It runs the same coaching flow and accepts an optional one-line idea to seed the conversation.

​
Linking an opportunity to a discovery

If Claude has shown you a pending discovery in your update and you want to respond to it, just say so:
Claude passes the discovery’s ID through to kowalah_create_opportunity, which:
  • Stamps the opportunity with the discovery and its project
  • Marks your invite as responded
  • Surfaces the opportunity to Kowalah’s triage queue alongside everyone else’s input
You can also start from the prompt menu with a discovery in mind — Submit an opportunity accepts a discovery ID and pulls the brief into the coaching prompt so the conversation is framed around what Kowalah is actually researching.

​
How it works

  1. A Claude workspace admin adds the Kowalah connector once (see setup in Claude)
  2. Each user signs in with their Kowalah account on first use (one-time OAuth)
  3. Claude calls Kowalah tools on your behalf, authenticated as you
  4. The server scopes every response to organizations you belong to and the role you hold in each one
The connector is stateless — each request is independently authenticated and scoped. Nothing is cached on Claude’s side.

​
What it can’t do

The connector reads widely, but writes narrowly: it can raise opportunities and maintain your own operating model, and that’s all. It does not provide:
  • Deleting anything. No connector tool deletes a record of any kind
  • Editing projects, deliverables, Expert Requests, or contracts. These are read-only here, use the platform
  • Editing an opportunity once it’s been raised
  • Anyone else’s training record, the cohort roster, or trainer notes
  • File uploads or document management
  • Organization settings or member management
  • Dashboard views or reporting
Operating-model edits are also gated by where you sit in your own org chart: you edit what you own or what’s below you, and propose everything else. See who can change what. For a full interactive experience, use the platform or the Kowalah Agent in Slack, Teams, or Google Chat.
The MCP connector is available to Kowalah Managed Services customers, and during a paid Kowalah programme.

Set up in Claude

Add the connector to your Claude workspace

Available tools

See what each tool does and how role affects it

Your operating model in Claude

Read the map, set targets and quality bars, propose changes

Security and data access

How the connector is scoped, gated, and verified