> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kowalah.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Access your Kowalah workspace from Claude using the Kowalah MCP Server at mcp.kowalah.com.

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 exposes three intent-shaped tools that cover the things customers actually want to do in chat:

<CardGroup cols={3}>
  <Card title="Get an update" icon="clipboard-list">
    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.
  </Card>

  <Card title="Find an accelerator" icon="rocket">
    Search the global Kowalah library and your organization's private accelerators for a prompt, GPT, or workflow that already solves your problem.
  </Card>

  <Card title="Raise an opportunity" icon="lightbulb">
    Capture a new idea, ask, or question for Kowalah to triage. Optionally link it to a discovery you've been invited to.
  </Card>
</CardGroup>

## Find the discoveries you're invited to

When Kowalah runs a [Discovery](/platform/discoveries), 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:

```text theme={null}
What's pending for me in Kowalah?
```

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](/platform/opportunities) 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:

```text theme={null}
I want to raise an opportunity with Kowalah about cleaning up
the way we onboard new suppliers
```

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

<Tip>
  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.
</Tip>

### 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:

```text theme={null}
I want to respond to the supplier onboarding discovery
```

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](/integrations/mcp/setup-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 is read-and-capture. It does not provide:

* Editing existing projects, deliverables, or Expert Requests (use the [platform](/platform/overview))
* File uploads or document management
* Organization settings or member management
* Dashboard views or reporting

For a full interactive experience, use the [platform](/platform/overview) or the [Kowalah Agent](/integrations/agent/overview) in Slack, Teams, or Google Chat.

<Info>
  The MCP connector is available to Kowalah Managed Services customers, and during a paid Kowalah programme.
</Info>

<CardGroup cols={2}>
  <Card title="Set up in Claude" icon="monitor" href="/integrations/mcp/setup-claude">
    Add the connector to your Claude workspace
  </Card>

  <Card title="Available tools" icon="wrench" href="/integrations/mcp/available-tools">
    See what each tool does and how role affects it
  </Card>
</CardGroup>