Skip to main content
The MCP connector (the Kowalah Claude Connector) puts your Kowalah workspace directly inside Claude. Anyone who uses Claude on the web or desktop gets instant access to your projects, deliverables, accelerators, and the opportunities pipeline — right alongside whatever they’re already working on.
The MCP connector is available to Kowalah Managed Services customers, and during a paid Kowalah programme. Learn more about how it works.

​
What you can do

The connector is built around the things people actually want to do in chat.

Get an update

A portfolio rollup, a focused view of any project / deliverable / Expert Request / opportunity, or a list of discovery briefs you’re invited to.

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’s team to triage, optionally linked to a discovery brief you’ve been invited to.

Check your training

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

Work your operating model

Read your coverage map, talk a process through step by step, and keep it true to how the work actually runs.

​
Work your operating model from Claude

This is the capability most teams underuse. Your AI Operating Model is available in full inside Claude: the coverage map, each function’s process portfolio, and any single process with its steps, current and target dispositions, quality evals, and the work already aimed at it.
Everyone in your organization can read the whole map. Editing depends on where the process sits relative to you: you edit what you own and what’s below you in the org tree, and propose changes to everything else. Claude knows which applies before it tries, so it offers the right next step rather than reporting a refusal. Admins and core team can edit anywhere in the organization. If someone should be able to edit but everything routes to a proposal, their home unit probably isn’t set.

The full walkthrough

Reading the map, setting targets and quality bars, and proposing changes to processes you don’t own

​
See what’s waiting for you

Ask Claude for an update and the connector returns a role-appropriate rollup plus any Discovery briefs you’ve been invited to respond to:
The pending_discoveries section shows each brief, its goal, the business value context, the close date, and the project it sits against. You only see your own invites — never anyone else’s, regardless of role.

​
Respond to a discovery from chat

If you’ve been invited to a discovery, you can submit your response without leaving Claude:
Claude walks you through goal, what good looks like, and the context Kowalah needs, then submits the opportunity with the discovery ID attached. The server:
  • Validates that you’re on the discovery’s audience
  • Stamps the opportunity with the discovery and its project
  • Marks your invite as responded so reminders stop

​
Raise a free-standing opportunity

Opportunities don’t have to come from a discovery. Anyone in your organization — admin, core team, or member — can raise one any time:
Claude checks the accelerator library first, sharpens the description with you, then submits and shows you the opportunity number (OPP-XXXX) so you can refer back to it.
Picking Submit an opportunity from Claude’s prompt menu starts the guided submission flow directly. It accepts an optional one-liner to seed the conversation.

​
Role-based access

The connector enforces the same visibility rules as the platform: Two things sit outside role:
  • Discovery invites are personal, so you always see your own pending discoveries whatever your role.
  • Training is personal: everyone sees their own record only, and only admins and core team can pull the anonymised org rollup.

​
Data security

  • Organization scoped, you only see data from organizations you belong to
  • Role-filtered, members only see what they raised or are a stakeholder on
  • Altitude-gated, operating-model edits are checked against your position in the org tree
  • Nothing deletes, no connector tool can delete a record of any kind
  • Client visibility, tasks, risks, and decisions are filtered to client-visible items
  • Discovery audience gate, opportunity submissions tagged with a discovery are rejected if you’re not on the audience
  • Stateless, each request is independently authenticated and nothing is cached

​
Set up the connector

Setup guide

Add the connector to your Claude workspace

Available tools reference

What each tool returns and how role affects it

Your operating model in Claude

Read the map, set targets, propose changes

Security and data access

How the connector is scoped and gated