The Kowalah Claude Connector exposes three intent-shaped tools plus a few slash commands. Each tool is scoped to organizations you belong to and filtered by your role in each one — so you never see anything Kowalah hasn’t given you access to in the platform.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.
Tools
kowalah_get_update
A single tool for any “how are things”, “what’s the status of X”, “what’s waiting for me” question. Pass an optional natural-language query; the server figures out whether you want a portfolio rollup, a focused view of a specific thing, or just your identity and organizations.
| You ask | You get |
|---|---|
What's going on in Kowalah? (no query) | A home view — your role-appropriate rollup, plus any pending discovery invites |
How's the procurement project? | A focused view of the matched project, deliverable, Expert Request, or opportunity |
What's ER-42 doing? | A focused view of that Expert Request |
Show me OPP-14 | A focused view of that opportunity |
Pending discoveries in the home view
If Kowalah is running a Discovery and you’re on the audience, the home view includes apending_discoveries section with:
- The discovery number (e.g.
DISC-0003) and name - The goal — what Kowalah is researching
- The business value context — why it matters
- The close date — when the discovery stops collecting responses
- The project the discovery sits against (if any)
What a focused view returns
| Entity | Includes |
|---|---|
| Project | Status, health, deliverables, milestones, client-visible risks and decisions, open Expert Requests, recent outcomes, your Kowalah contact |
| Deliverable | Stage, progress, parent project, client-visible tasks, open Expert Requests, outcomes captured against it |
| Expert Request | Status, progress, recent progress updates, outcomes, assigned expert contact |
| Opportunity | Status, content, ICE score, source, what (if anything) it’s been promoted to |
kowalah_find_accelerator
Searches Kowalah’s global accelerator library plus your organization’s private accelerators for a reusable prompt, GPT, training, or workflow.
Use this whenever you’re about to raise a request for help — there may already be something on the shelf you can take and run with.
kowalah_create_opportunity
The single inbound entry point for everything a customer wants to raise with Kowalah — a question, an idea, a piece of work to scope, a new project to consider. Anyone in your organization can submit, regardless of role.
The customer doesn’t have to decide whether the work is an Expert Request, a Deliverable, or a Project. Kowalah’s team triages from there.
Before submitting, Claude is expected to:
- Check the accelerator library for something that already solves the problem
- Make sure the description is at least a paragraph (~80+ characters of real context — goal, what good looks like, anything Kowalah should know)
- Ask which organization the opportunity is for (if you belong to more than one)
Linking an opportunity to a discovery
If you’re responding to a Kowalah discovery you’ve been invited to, Claude passes thediscovery_id through when it submits. The server then:
- Validates that you’re actually on the discovery’s audience
- Stamps the opportunity with the discovery and its project
- Marks your audience invite as responded so reminders stop
Prompts
The connector also registers a few prompts you can pick from Claude’s prompt menu (the ”+” attachment / slash menu, depending on which Claude client you’re using). Some are role-gated.| Prompt | Who sees it | What it does |
|---|---|---|
| Submit an opportunity | Everyone | Guided coaching flow that walks you through goal → what good looks like → context, then submits the opportunity. Accepts an optional one-line idea, and an optional discovery ID if you’re responding to a brief |
| Programme update | Admin and core team only | Pulls a structured programme update across your portfolio |
| Expert Request credits and quota | Admin and core team only | Summarises Expert Request credits used vs. quota under each active contract |
What your role changes
| Role | Update view | Opportunities visible | Projects, deliverables, ERs visible | Can raise opportunities |
|---|---|---|---|---|
| Admin | Full org rollup | Every opportunity in the org | All | Yes |
| Core team | Full org rollup | Every opportunity in the org | All | Yes |
| Member | Personal rollup | Only the ones you raised | Only the ones you’re a stakeholder on | Yes |
no_match response for a known reference number usually means the item exists but you’re not permitted to see it — not that it doesn’t exist. This is most common for members who aren’t on the stakeholder list for a given project, deliverable, or Expert Request.
Discovery invites are different: they’re personal to you, so you always see your own pending discoveries regardless of role.
Data filtering
The connector enforces visibility on the server side:- Organization scoping — only data from organizations you belong to is ever returned
- Role-based filtering — members only see what they raised or are a stakeholder on
- Client visibility flags — tasks, risks, and decisions are filtered to client-visible items
- Discovery audience gate — opportunity submissions tagged with a
discovery_idare rejected if you’re not on the audience - Field filtering — internal fields (Kowalah team assignments, contract values, payment details) are not exposed
Set up in Claude
Add the connector to your Claude workspace
Roles and permissions
Full role reference