Back to website ↗

Reference

Connect an AI assistant to Serre

On this page

Connect an MCP-capable assistant to work in your Serre workspace from your own conversation: read your library, accounts and case results, and — once your workspace is enrolled — set the workspace up and build business cases.

Serre Connect is included on every paid plan.

What your assistant can do#

Every key can read: your company profiles, solutions (with their value story, claims, drivers and value model), personas, evidence, accounts, saved case results and first-run readiness. Reads never use AI credits or business cases.

A full-access key on an enrolled workspace can also write, through the same guided tools the app uses:

  • Set the workspace up — create the company profile, its solutions, the buying committee and evidence; research a company or a solution; run a value capture to draft claims from your product material; and complete first-run setup once the required pieces are in place.
  • Build cases — plan and start a case for an account, develop its buyer context, author and attach drivers, set inputs and pricing, run the checks, calculate, finalize and share.

Everything it does happens as you, inside your workspace, with your current permissions. Every write is checked against the record as it stands (a teammate's edit in between is never overwritten) and recorded against your key. Removing membership, downgrading a role or revoking a key changes access on the next request. Use the MCP connection endpoint; API keys do not grant general REST access.

When a check finding blocks a case. A case can't be finalized while a blocking check finding is open. If one doesn't hold for the case, such as "no buyer-stated input" on a case built without discovery, your assistant can dispute it with a written reason. The dispute and its reason are recorded on the case, so anyone reviewing it can see why the finding was cleared. Your assistant never marks an input as customer-provided to get past it when the buyer didn't confirm the number.

1. Create a key#

Go to Settings → Security & access → API keys and click New key in the API keys section. The row turns into the create form. Give the key a Name that tells you where it lives, like "Claude Code on my laptop", so you know which one to turn off later, then click "Create key".

Setting up a brand-new workspace with your assistant? The welcome screen links straight to this page ("Create a Serre Connect key →"), so you can mint the key before first-run setup exists.

The form asks for two more choices:

Expires. Keys expire after 90 days unless you say otherwise. Shorten it for a short piece of work, or choose "Never" if the key lives somewhere you control and you'd rather manage it by hand. An expired key stops working exactly like a revoked one.

Access. Choose "Read-only" for inspection, or "Full access" for the guided write tools. You can't change it after the key is created. A full-access key can only write once the workspace is enrolled (next step); until then it reads like a read-only key.

Copy the key immediately with "Copy key". It's shown once and never again. If you lose it, revoke it and create another. That's normal, not a problem.

2. Enrol the workspace for guided writes#

Go to Settings → API & MCP. In the Serre Connect section, Guided writes explains what enrollment allows and shows whether your workspace is enrolled. An admin or the owner clicks "Enroll workspace", under the explanation, to switch it on (or "Withdraw" to stop new writes at once). Enrolment is off by default, per workspace, and every change is recorded with who made it and when.

Use Settings → API & MCP → Set up an assistant for the client instructions and setup prompt. Your keys stay under Security & access.

Enrolment applies to full-access keys only; read-only keys are unaffected.

3. Add the key to your assistant#

After you create the key, copy it with "Copy key" before selecting "Done" or leaving the page. The key will not be shown again.

Serre Connect is a streamable HTTP MCP server at https://platform.serre.app/api/mcp. It authenticates with your personal key, sent on every request as Authorization: Bearer YOUR-KEY. Replace YOUR-KEY with the key you just copied. Treat it like a password. The key is personal, and the assistant acts as you.

Settings → API & MCP → Set up an assistant shows the same command, configuration, or details. Those instructions use YOUR-KEY as a placeholder. Replace it with the key you copied before you use them, and keep the completed command private.

Claude Code (terminal)#

In a terminal, run this as one command:

claude mcp add --transport http serre https://platform.serre.app/api/mcp --scope user --header "Authorization: Bearer YOUR-KEY"

--scope user stores the connection in your user configuration, so Serre is available in every project on this machine and stays private to you.

Check it from the terminal:

claude mcp get serre

Or, inside Claude Code, run /mcp. It should say Connected. Start a new session after you add the connection.

Anthropic's reference: MCP in Claude Code.

Claude Desktop#

The desktop app runs Serre through a local bridge. You need Node.js 18 or newer.

  1. Open Settings → Developer → Edit Config. That opens claude_desktop_config.json. On macOS the file lives in ~/Library/Application Support/Claude/. On Windows it lives in %APPDATA%\Claude\.
  2. Add a serre server. If the file already lists other servers, add this entry inside the existing mcpServers object.
{
  "mcpServers": {
    "serre": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://platform.serre.app/api/mcp",
        "--header",
        "Authorization:${SERRE_AUTH}"
      ],
      "env": {
        "SERRE_AUTH": "Bearer YOUR-KEY"
      }
    }
  }
}

The header is Authorization:${SERRE_AUTH} with no space after the colon. That avoids a known Windows bug in the bridge. The space belongs in the value, after Bearer.

Fully quit Claude Desktop from the menu, then open it again. Look for Serre in the tools menu.

Claude web (claude.ai)#

Open Customize → Connectors (also under Settings), choose Add custom connector, and enter https://platform.serre.app/api/mcp. Choose No sign-in. Under Request headers, add a header named authorization with the value Bearer YOUR-KEY, including the space after Bearer. Claude sends that value exactly as you type it.

Request headers is a beta Anthropic is rolling out, and some accounts do not see it yet. When the option is missing, use Claude Code or Claude Desktop.

On Team and Enterprise, an Owner sets a connector up once for the organization, and every member would share that one key. Until Serre supports sign-in with your own account, use Claude Code or Claude Desktop.

Anthropic's references: Add a connector that isn't in the directory and Get started with custom connectors.

Other MCP clients#

Use https://platform.serre.app/api/mcp and an Authorization: Bearer YOUR-KEY header.

4. Ask for what you want#

Talk to your assistant normally. A good first request is simply "list my accounts". If it comes back with your real accounts, the connection is working.

Setting up a new workspace. Ask:

Set up my Serre workspace for Acme. Start from acme.example, then tell me what's still missing before we're ready.

A good assistant will research the site, draft the company profile and solutions for your review, add the buying committee and evidence you describe, link the value drivers that quantify each solution, and read the readiness checklist. Setup is only completed when every item on that checklist is met — the company is saved, the flagship solution is saved with a description of how it creates value, at least one claim is approved for business cases, and at least one value driver has starting inputs — and the assistant will tell you what is open rather than skip it.

Working an existing case. Provide its Serre workspace link or case ID and ask:

Read the saved results for this case and help me review the conclusions.

Numbers are never applied from a conversation without a reviewable proposal and an explicit decision, and nothing is shared with a buyer until you ask for the link.

Try one of these. Once Serre appears in your assistant's tool list, any of these is a good first request:

  • Research a buyer. "Find our Acme account and summarize the context already saved in Serre."
  • Build a governed case. "Plan a business case for Acme, then ask me before creating or changing anything."
  • Review assumptions. "Show the current inputs, sources, pricing, and reasonableness findings for this case."
  • Prepare delivery. "Calculate the case, explain the caveats, and tell me which human reviews remain before sharing."

What costs what. Research and drafting steps use AI credits from your workspace allowance: researching a company, solution or persona, drafting a buyer brief, suggesting drivers or inputs, running a value capture or the library agent, and the optional Val Review. Serre's tools tell your assistant what each step costs, so it can check with you first. Calculating a case uses a business case from your allowance the first time. Reads are free.

5. Turn a key off#

Go back to Settings → Security & access → API keys, click "Revoke" next to the key, then "Revoke key". It stops working immediately. Buyer links you already shared keep working. Anything using it loses access at once, including any assistant still connected.

Revoke a key whenever you finish testing, change laptop, or if you think the key has been seen by anyone else. Create a new one whenever you need it; there's no limit and no cost.

The list shows when each key expires and flags one that's about to, so you can replace it before it stops working rather than after.

Good practice#

  • One key per place you use it, not one key everywhere. Then turning off a laptop doesn't disconnect everything else.
  • Keys are personal. Yours acts as you, with your permissions. Don't share it with a colleague. Have them create their own.
  • Keep the connection separate from browser sign-in. Send its API key to the MCP endpoint without browser session cookies; mixed credentials are rejected.
  • Withdraw enrolment when you're done experimenting. Reads keep working; new writes stop at once.

Documentation

Browse documentation or search for a topic

Selected: Set up your company profile

Get startedSet up your company profile

Your company profile is the foundation everything else builds on — solutions, drivers, and business cases all inherit context from it. This guide shows you how to cr…

Get startedManage your solutions

Solutions are the products you sell. Keeping them well-described pays off everywhere downstream: value drivers map to them, and business cases group benefits under t…

Get startedMeet Val, your value-engineering copilot

Val is the AI copilot built into Serre. Wherever you see the Val button, click it (or press ⌘J / Ctrl+J) to open a chat panel beside the page. Describe what you want…

Build and share a caseCreate an account

An account is a company you sell to: a prospect or an existing customer. Get the profile right and every business case for that account starts from solid ground. Thi…

Build and share a caseBuild a value driver

This guide walks you through the Driver Studio — one editor for creating and refining the formulas that power your business cases. New here? Read What is a value dri…

Build and share a caseBuild a business case

When you finish, you'll have a calculated, reviewed business case for one account, ready to export or share. The case walks you through eight steps, shown across the…

Build and share a caseExport and share a business case

When you finish this guide, your buyer has the case in hand — as a document, a private link, or both — and you're ready for the conversation. Everything happens in t…

Understand the foundationsWhat is a value driver?

A value driver is a single, measurable way your product creates value for a buyer — for example "Reduced Manual Billing Time" or "Lower Infrastructure Spend". It's t…

Understand the foundationsWhat is a business case?

A business case is the deliverable Serre exists to produce: a quantified, defensible answer to the question every buyer eventually asks — "what is this actually wort…

Understand the foundationsHow Serre calculates ROI

Every number in a Serre business case comes from transparent math you can read — formulas with inputs you control. The AI helps you draft formulas, suggest inputs, a…

Workspace and supportManage your team and plan

Everything account-related lives under Settings: your profile, your teammates, and your plan's allowances. Your profile Settings has five groups: Personal, Workspace…

Workspace and supportCommon questions

Quick answers to the issues and questions we hear most. Each entry: what you're seeing, why, and what to do. Account & sign-in I can't sign in. Check for typos first…

ReferenceConnect an AI assistant to Serre

Connect an MCP-capable assistant to work in your Serre workspace from your own conversation: read your library, accounts and case results, and — once your workspace …

ReferenceSerre Connect tool reference

Every tool your assistant can use once it is connected to Serre, with the exact arguments each one takes. This page is generated from the connection itself, so it al…