@probo/skills 0.2.2 → 0.3.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "probo",
-  "version": "0.1.0",
+  "version": "0.3.0",
   "description": "Open-source compliance workflows powered by Probo MCP (Claude Code, Codex, OpenCode)",
   "author": {
     "name": "Probo Inc",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "probo",
-  "version": "0.1.0",
+  "version": "0.3.0",
   "description": "Open-source compliance workflows powered by Probo MCP (Codex, OpenCode, Claude Code)",
   "author": {
     "name": "Probo Inc",

package/.mcp.json

@@ -1,8 +1,12 @@
 {
   "mcpServers": {
-    "probo": {
+    "probo-us": {
       "type": "http",
-      "url": "${PROBO_BASE_URL}/mcp/v1"
+      "url": "https://us.probo.com/api/mcp/v1"
+    },
+    "probo-eu": {
+      "type": "http",
+      "url": "https://eu.probo.com/api/mcp/v1"
     }
   }
 }

package/COMPATIBILITY.md

@@ -22,31 +22,69 @@ SOFTWARE.
 
 # Multi-agent compatibility
 
-`@probo/skills` targets **Claude Code**, **Codex**, **OpenCode**, and
-other MCP-capable agents (including **Cursor**). The portable core is Probo
-MCP plus Agent Skills–compatible `SKILL.md` files.
+`@probo/skills` is an [Agent Plugins 1.0.0](https://agent-plugins.org/)
+package. The portable core is `plugin.json`, Agent Skills under `skills/`, and
+Probo MCP servers in `mcp.json`. Client-specific manifests carry the same
+components to **Claude Code**, **Codex**, **OpenCode**, and **Cursor** until
+those clients load the portable package directly.
 
-## What works where
+## Portable package (Agent Plugins 1.0.0)
+
+```
+plugin.json    # $schema + plugin identity (spec §5)
+skills/        # one directory per skill, each with SKILL.md (spec §7.1)
+mcp.json       # $schema + mcpServers (spec §7.2)
+```
+
+Both documents declare
+`https://agent-plugins.org/schemas/1.0.0/{plugin,mcp}.schema.json`, and the
+spec requires the two versions to match.
+
+Commands, marketplace catalogs, and the client manifests are outside the v1
+format — Agent Plugins v1 standardizes only skills and MCP servers. Clients
+ignore the extra files.
 
-| Component | Claude Code | Codex | OpenCode | Cursor |
-| --- | --- | --- | --- | --- |
-| Probo MCP (OAuth) | ✅ Plugin `.mcp.json` | ✅ `.codex-plugin` + `.mcp.json` | ✅ Manual MCP config | ✅ IDE MCP settings |
-| Skills (`SKILL.md`) | ✅ `skills/` | ✅ `skills/` via `.codex-plugin` | ✅ `.opencode/skills/` or `.claude/skills/` | ✅ Copy/symlink to `.cursor/skills/` |
-| Commands | ✅ `commands/` → `/probo:…` | ⚠️ Use skills instead | ⚠️ Native `skill` tool | ❌ Use skill or rules |
-| Plugin manifest | `.claude-plugin/` | `.codex-plugin/` | Discovery paths (no manifest) | No native manifest |
-| Marketplace catalog | `.claude-plugin/marketplace.json` (repo root or package) | `.agents/plugins/marketplace.json` (repo root or package) | — | — |
+## Probo MCP servers
 
-## Probo MCP (all agents)
+`mcp.json` ships both hosted instances as Streamable HTTP servers:
 
-Set the instance URL:
+| Server | Endpoint |
+| --- | --- |
+| `probo-us` | `https://us.probo.com/api/mcp/v1` |
+| `probo-eu` | `https://eu.probo.com/api/mcp/v1` |
+
+Connect the server for your region. Skills that need to discover the region
+call `listOrganizations` on each connected server and keep the one that returns
+the target organization.
+
+Authentication is **OAuth 2.0** only, discovered from
+`/.well-known/oauth-protected-resource` on the instance root. Never configure a
+static bearer token: Agent Plugins treats `headers` as visible package data,
+and a pre-set `Authorization` header also stops Claude Code from starting the
+OAuth flow.
+
+### Self-hosted instances
+
+Agent Plugins 1.0.0 performs no placeholder or environment-variable expansion
+in remote MCP URLs (spec §7.2.1), so a self-hosted endpoint cannot ship in the
+package. Add it in the agent:
 
 ```bash
-export PROBO_BASE_URL="https://your-probo-instance.example.com"
+claude mcp add --transport http probo https://probo.example.com/api/mcp/v1
+codex mcp add --transport http probo https://probo.example.com/api/mcp/v1
 ```
 
-Endpoint: `${PROBO_BASE_URL}/mcp/v1` (HTTP, OAuth 2.0). Do not configure a
-static bearer token — OAuth discovery uses
-`/.well-known/oauth-protected-resource`.
+The MCP path is always `<instance-root>/api/mcp/v1`.
+
+## What works where
+
+| Component | Agent Plugins client | Claude Code | Codex | OpenCode | Cursor |
+| --- | --- | --- | --- | --- | --- |
+| Probo MCP (OAuth) | ✅ `mcp.json` | ✅ `.mcp.json` | ✅ `.codex-plugin` + `.mcp.json` | ✅ Manual MCP config | ✅ IDE MCP settings |
+| Skills (`SKILL.md`) | ✅ `skills/` | ✅ `skills/` | ✅ `skills/` via `.codex-plugin` | ✅ `.opencode/skills/` or `.claude/skills/` | ✅ Copy/symlink to `.cursor/skills/` |
+| Commands | ❌ Outside v1 | ✅ `commands/` → `/probo:…` | ⚠️ Use skills instead | ⚠️ Native `skill` tool | ❌ Use skill or rules |
+| Plugin manifest | `plugin.json` | `.claude-plugin/` | `.codex-plugin/` | Discovery paths (no manifest) | No native manifest |
+| Marketplace catalog | — | `.claude-plugin/marketplace.json` (repo root or package) | `.agents/plugins/marketplace.json` (repo root or package) | — | — |
 
 ### Claude Code
 
@@ -58,7 +96,7 @@ claude plugin marketplace add getprobo/probo
 # or, from a local clone:
 claude plugin marketplace add .
 claude plugin install probo@probo
-claude mcp login probo   # or /mcp in session
+claude mcp login probo-us   # or /mcp in session
 /probo:access-review Q3 GitHub review
 ```
 
@@ -67,7 +105,7 @@ claude mcp login probo   # or /mcp in session
 ```bash
 claude plugin marketplace add ./packages/skills/.claude-plugin
 claude plugin install probo@probo
-claude mcp login probo
+claude mcp login probo-us
 ```
 
 Or install the plugin directory directly:
@@ -86,7 +124,7 @@ codex plugin marketplace add getprobo/probo
 # or, from a local clone:
 codex plugin marketplace add .
 codex plugin install probo@probo
-codex mcp login probo
+codex mcp login probo-us
 ```
 
 **From the package directory** (catalog at
@@ -95,14 +133,14 @@ codex mcp login probo
 ```bash
 codex plugin marketplace add ./packages/skills
 codex plugin install probo@probo
-codex mcp login probo
+codex mcp login probo-us
 ```
 
 Or install the plugin directory directly:
 
 ```bash
 codex plugin install ./packages/skills
-codex mcp login probo
+codex mcp login probo-us
 ```
 
 Skills load from `./skills/` via `.codex-plugin/plugin.json`. The repo-root
@@ -126,12 +164,14 @@ ln -s ../../packages/skills/skills/open-source-compliance .opencode/skills/open-
 [`opencode-claude-code-bridge`](https://www.npmjs.com/package/opencode-claude-code-bridge)
 to import Claude plugins and MCP configs into OpenCode.
 
-Configure Probo MCP in `opencode.json` or global OpenCode MCP settings, then
-authenticate. Invoke via the native `skill` tool (`access-review`).
+Configure a Probo MCP server in `opencode.json` or global OpenCode MCP
+settings, then authenticate. Invoke via the native `skill` tool
+(`access-review`).
 
 ### Cursor
 
-1. Add Probo MCP in Cursor settings (HTTP URL: `${PROBO_BASE_URL}/mcp/v1`,
+1. Add a Probo MCP server in Cursor settings (HTTP URL:
+   `https://us.probo.com/api/mcp/v1` or `https://eu.probo.com/api/mcp/v1`,
    OAuth).
 2. Copy or symlink skills into `.cursor/skills/`:
 
@@ -146,9 +186,11 @@ Reference the skill in chat or add a Cursor rule pointing at the skill.
 
 | Path | Portable? |
 | --- | --- |
+| `plugin.json` | ✅ Agent Plugins manifest (spec §5) |
+| `mcp.json` | ✅ Agent Plugins MCP configuration (spec §7.2) |
 | `skills/<name>/SKILL.md` | ✅ Agent Skills standard |
 | `skills/<name>/references/*.md` | ✅ Relative to skill directory |
-| `.mcp.json` with `${PROBO_BASE_URL}` | ✅ Standard env var |
+| `.mcp.json` | Claude Code and Codex mirror of `mcp.json` (`type: http`) |
 | `${CLAUDE_PLUGIN_ROOT}` | ❌ Claude Code only — avoid in skill bodies |
 | `commands/*.md` | Claude Code slash commands only |
 
@@ -159,13 +201,15 @@ directory is discovered, regardless of which agent loads it.
 
 ```
 @probo/skills/
+  plugin.json                        # Agent Plugins manifest
+  mcp.json                           # Agent Plugins MCP configuration
+  skills/                            # Shared skills (all agents)
+  commands/                          # Claude Code commands only
+  .mcp.json                          # Claude Code / Codex MCP wiring
   .claude-plugin/plugin.json         # Claude Code manifest
   .claude-plugin/marketplace.json    # Claude marketplace (npm)
   .codex-plugin/plugin.json          # Codex manifest
   .agents/plugins/marketplace.json   # Codex marketplace (package-local)
-  .mcp.json                          # Shared MCP wiring
-  skills/                            # Shared skills (all agents)
-  commands/                          # Claude Code commands only
 ```
 
 Repo root (monorepo / `getprobo/probo` Git installs):
@@ -174,3 +218,14 @@ Repo root (monorepo / `getprobo/probo` Git installs):
 .claude-plugin/marketplace.json      # Claude marketplace → packages/skills
 .agents/plugins/marketplace.json     # Codex marketplace → packages/skills
 ```
+
+## Validation
+
+```bash
+npm --workspace @probo/skills run validate
+```
+
+`scripts/validate.mjs` enforces the Agent Plugins closed manifest and MCP
+schemas (canonical `$schema` values, plugin name constraints, transport
+variants, literal HTTPS URLs, no credential headers), Agent Skills frontmatter
+rules, and that `.mcp.json` stays in lockstep with `mcp.json`.

package/README.md

@@ -1,20 +1,49 @@
 # @probo/skills
 
-Multi-agent compliance skills for open-source GRC workflows. Ships Agent
-Skills–compatible instructions and wires agents to the [Probo MCP
-API](https://github.com/getprobo/probo/tree/main/pkg/server/api/mcp/v1) via
+Multi-agent compliance skills for open-source GRC workflows. Ships an
+[Agent Plugins 1.0.0](https://agent-plugins.org/) package: Agent
+Skills–compatible instructions plus portable MCP wiring to the [Probo MCP
+API](https://github.com/getprobo/probo/tree/main/pkg/server/api/mcp/v1) over
 OAuth 2.0.
 
-**Supported agents:** Claude Code, Codex, OpenCode, Cursor (MCP + skills).
+**Supported agents:** any Agent Plugins client, plus Claude Code, Codex,
+OpenCode, and Cursor through their own plugin or MCP configuration.
 
-Marketplace catalogs: `.claude-plugin/marketplace.json` at the repo root or
-under `packages/skills/` (Claude Code), `.agents/plugins/marketplace.json` at
-the repo root or under `packages/skills/` (Codex). See
+The portable package is `plugin.json`, `skills/`, and `mcp.json` at the package
+root. Client-specific manifests (`.claude-plugin/`, `.codex-plugin/`,
+`.mcp.json`) and marketplace catalogs sit alongside it. See
 [COMPATIBILITY.md](./COMPATIBILITY.md).
 
+## Probo MCP servers
+
+Both hosted Probo instances ship in `mcp.json`; connect the one for your
+region and sign in with OAuth 2.0.
+
+| Server | Endpoint |
+| --- | --- |
+| `probo-us` | `https://us.probo.com/api/mcp/v1` |
+| `probo-eu` | `https://eu.probo.com/api/mcp/v1` |
+
+Agent Plugins 1.0.0 defines no placeholder expansion for remote MCP URLs, so a
+self-hosted instance is added in the agent instead of in the package:
+
+```bash
+claude mcp add --transport http probo https://probo.example.com/api/mcp/v1
+```
+
+No API token or bearer header belongs in any of these configs. Probo MCP
+authenticates with OAuth 2.0, discovered from
+`/.well-known/oauth-protected-resource` on the instance root.
+
 ## Install
 
-### From GitHub or npm
+### Agent Plugins client
+
+Point the client at the package root (`packages/skills` in a clone, or the
+installed `@probo/skills` directory). It reads `plugin.json`, discovers the
+skills under `skills/`, and loads both servers from `mcp.json`.
+
+### Claude Code
 
 **From GitHub** (repo-root catalog at `.claude-plugin/marketplace.json`):
 
@@ -23,6 +52,7 @@ claude plugin marketplace add getprobo/probo
 # or, from a local clone:
 claude plugin marketplace add .
 claude plugin install probo@probo
+claude mcp login probo-us   # or /mcp in session
 ```
 
 **From the package directory** (catalog at
@@ -34,35 +64,6 @@ claude plugin marketplace add ./packages/skills/.claude-plugin
 claude plugin install probo@probo
 ```
 
-When consuming the published package, the package-level marketplace entry
-resolves `@probo/skills` from npm (see
-`packages/skills/.claude-plugin/marketplace.json`).
-
-### Configure Probo MCP
-
-Set your Probo instance URL before starting Claude Code:
-
-```bash
-export PROBO_BASE_URL="https://your-probo-instance.example.com"
-```
-
-The plugin `.mcp.json` connects to `${PROBO_BASE_URL}/mcp/v1`. Probo MCP
-authenticates with **OAuth 2.0** — no API token or bearer header is required in
-the plugin config. On first use, sign in from Claude Code:
-
-```text
-/mcp
-```
-
-Or from your shell:
-
-```bash
-claude mcp login probo
-```
-
-Claude Code discovers Probo's authorization server via
-`/.well-known/oauth-protected-resource` and stores tokens securely.
-
 ### Local development
 
 ```bash
@@ -73,9 +74,10 @@ claude --plugin-dir ./packages/skills
 
 | Component | Location | Purpose |
 | --- | --- | --- |
-| MCP | `.mcp.json` | Probo API connection |
+| Manifest | `plugin.json` | Agent Plugins 1.0.0 plugin identity |
+| MCP | `mcp.json` | Portable hosted Probo servers |
 | Skills | `skills/` | Compliance workflows |
-| Commands | `commands/` | `access-review`, `missing-signatures` — semi-auto workflows |
+| Commands | `commands/` | `access-review`, `missing-signatures` — semi-auto workflows (Claude Code) |
 
 Skills: `/probo:<skill-name>` (e.g. `/probo:open-source-compliance`, `/probo:missing-signatures`).
 

package/mcp.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
+  "mcpServers": {
+    "probo-us": {
+      "type": "streamable-http",
+      "url": "https://us.probo.com/api/mcp/v1"
+    },
+    "probo-eu": {
+      "type": "streamable-http",
+      "url": "https://eu.probo.com/api/mcp/v1"
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@probo/skills",
-  "version": "0.2.2",
+  "version": "0.3.0",
   "description": "Multi-agent compliance skills for open-source GRC (Claude Code, Codex, OpenCode) powered by Probo MCP",
   "private": false,
   "scripts": {
@@ -18,6 +18,8 @@
     ".agents",
     "skills",
     "commands",
+    "plugin.json",
+    "mcp.json",
     ".mcp.json",
     "README.md",
     "COMPATIBILITY.md"
@@ -25,6 +27,7 @@
   "keywords": [
     "claude-code",
     "agent-skills",
+    "agent-plugins",
     "codex",
     "opencode",
     "probo",
@@ -34,6 +37,9 @@
     "open-source"
   ],
   "license": "MIT",
+  "devDependencies": {
+    "js-yaml": "^4.3.1"
+  },
   "repository": {
     "type": "git",
     "url": "git+https://github.com/getprobo/probo.git",

package/plugin.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "probo",
+  "version": "0.3.0",
+  "description": "Open-source compliance workflows powered by the Probo MCP API",
+  "author": {
+    "name": "Probo Inc",
+    "email": "hello@probo.com",
+    "url": "https://www.probo.com"
+  },
+  "homepage": "https://github.com/getprobo/probo/tree/main/packages/skills",
+  "repository": "https://github.com/getprobo/probo",
+  "license": "MIT",
+  "keywords": [
+    "probo",
+    "compliance",
+    "grc",
+    "mcp",
+    "agent-skills",
+    "open-source"
+  ]
+}

package/skills/access-review/SKILL.md

@@ -18,13 +18,30 @@ Before executing, read these files **relative to this skill directory**:
 
 ## Preconditions
 
-1. Probo MCP must be connected. If tools fail with auth errors, stop and tell
-   the user to complete OAuth sign-in for the Probo MCP server in their agent
-   (Claude Code: `/mcp` or `claude mcp login probo`; Codex: `codex mcp login
-   probo`; OpenCode/Cursor: configure MCP in settings then authenticate).
-2. Resolve the campaign from `$ARGUMENTS` (name match or GID). If ambiguous,
-   list `listAccessReviewCampaigns` results and ask the user to pick one.
-3. Campaign `status` must be `IN_PROGRESS` or `PENDING_ACTIONS`. Stop with a
+1. A Probo MCP server must be connected. The plugin ships two hosted servers,
+   `probo-us` and `probo-eu`; self-hosted instances are configured in the agent.
+   If tools fail with auth errors, stop and tell the user to complete OAuth
+   sign-in for that server (Claude Code: `/mcp` or `claude mcp login probo-us`;
+   Codex: `codex mcp login probo-us`; OpenCode/Cursor: configure MCP in settings
+   then authenticate).
+2. Resolve **the server**, then **the organization**. These are separate
+   choices: one server can hold several organizations, and the caller can have
+   organizations on more than one server. Settle both before any campaign call,
+   because `listAccessReviewCampaigns` requires `organization_id`.
+   - **Server.** Use the server for the region the user names, or the only
+     connected server when there is one. Otherwise call `listOrganizations` on
+     each connected server and take the server whose organizations uniquely
+     match the one the user named. Never infer the region from a merely
+     non-empty result — when the match is not unique, show each server with the
+     organizations it returned and ask which to use.
+   - **Organization.** Once the server is settled, call `listOrganizations` on
+     it unless an earlier probe already returned its organizations. Take the
+     unique name match, or the only organization when the server returns one.
+     Otherwise list them and ask the user to pick.
+3. Resolve the campaign from `$ARGUMENTS` (name match or GID) within that
+   organization. If the campaign is ambiguous, list `listAccessReviewCampaigns`
+   results and ask the user to pick one.
+4. Campaign `status` must be `IN_PROGRESS` or `PENDING_ACTIONS`. Stop with a
    clear message for `DRAFT`, `COMPLETED`, or `CANCELLED`.
 
 ## Working notes file

package/skills/access-review/references/mcp-tools.md

@@ -1,7 +1,26 @@
 # Access review MCP tools
 
-All tools are on the Probo MCP server (`probo`). Read each tool schema before
-calling.
+All tools are on a Probo MCP server (`probo-us`, `probo-eu`, or a self-hosted
+server configured in the agent). Read each tool schema before calling.
+
+## Organization scope
+
+### `listOrganizations`
+
+List organizations the caller can access on the server it is called on. No
+required input, so it serves two distinct purposes:
+
+1. **Choosing a server** when the region is unknown — call it on each connected
+   server. A non-empty result does not identify the region, since the caller can
+   have organizations on both. Only a unique match for the organization the user
+   named settles it; otherwise show each server with its organizations and ask.
+2. **Choosing an organization** on a server that is already settled — including
+   a single self-hosted instance serving several organizations. Take the unique
+   name match, or the only organization when the server returns one, and
+   otherwise list them and ask.
+
+Either way the organization must be resolved before `listAccessReviewCampaigns`,
+which requires `organization_id`.
 
 ## Read
 
@@ -10,7 +29,7 @@ calling.
 List campaigns for an organization. Use to resolve `$ARGUMENTS` to a campaign
 when the user provides a name instead of a GID.
 
-Required: `organization_id`
+Required: `organization_id` — resolve the organization before calling this.
 
 ### `listAccessEntries`
 

package/skills/compliance-portal-commitments/SKILL.md

@@ -48,9 +48,9 @@ Commitments must trace to controls the company genuinely has. The source of trut
 **published policies** in Probo, not general knowledge about SOC 2 or ISO 27001.
 
 1. **Find the Probo MCP and the organization.** This environment may expose more than one Probo MCP
-   server (for example a US and an EU instance). Call `listOrganizations` on each until you find the one
-   that returns the target company, and use that server for every later call. Match the organization the
-   user named and capture its `id`.
+   server (the plugin ships hosted `probo-us` and `probo-eu`, and self-hosted instances add their own).
+   Call `listOrganizations` on each until you find the one that returns the target company, and use that
+   server for every later call. Match the organization the user named and capture its `id`.
 2. **List the published policies.** Call `listDocuments` with `document_types: ["POLICY"]`. Policies with
    a `current_published_major` are published.
 3. **Read the actual content.** `getDocument` returns metadata only. To get the text, call

package/skills/missing-signatures/SKILL.md

@@ -21,10 +21,14 @@ Before executing, read these files **relative to this skill directory**:
 
 ## Preconditions
 
-1. Probo MCP must be connected. If tools fail with auth errors, stop and tell
-   the user to complete OAuth sign-in for the Probo MCP server in their agent
-   (Claude Code: `/mcp` or `claude mcp login probo`; Codex: `codex mcp login
-   probo`; OpenCode/Cursor: configure MCP in settings then authenticate).
+1. A Probo MCP server must be connected. The plugin ships two hosted servers,
+   `probo-us` and `probo-eu`; self-hosted instances are configured in the agent.
+   Use the server for the user's region, and when the region is unknown call
+   `listOrganizations` on each connected server and keep the one that returns
+   the organization. If tools fail with auth errors, stop and tell the user to
+   complete OAuth sign-in for that server (Claude Code: `/mcp` or
+   `claude mcp login probo-us`; Codex: `codex mcp login probo-us`;
+   OpenCode/Cursor: configure MCP in settings then authenticate).
 2. Resolve the organization from `$ARGUMENTS` (name match or GID). If ambiguous,
    call `listOrganizations` and ask the user to pick one.
 3. This skill is **reporting only**. Do not request signatures, cancel requests,

package/skills/missing-signatures/references/mcp-tools.md

@@ -1,7 +1,7 @@
 # Missing signatures MCP tools
 
-All tools are on the Probo MCP server (`probo`). Read each tool schema before
-calling.
+All tools are on a Probo MCP server (`probo-us`, `probo-eu`, or a self-hosted
+server configured in the agent). Read each tool schema before calling.
 
 ## Organization scope
 

package/skills/open-source-compliance/SKILL.md

@@ -11,10 +11,13 @@ first.
 
 ## Before you start
 
-1. Confirm the Probo MCP server is connected. If not, ask the user to run
-   `/mcp` or `claude mcp login probo` to complete the OAuth 2.0 sign-in.
+1. Confirm a Probo MCP server is connected. The plugin ships two hosted
+   servers, `probo-us` and `probo-eu`; self-hosted instances are configured in
+   the agent. If none is connected, ask the user to run `/mcp` or
+   `claude mcp login probo-us` to complete the OAuth 2.0 sign-in.
 2. Identify the target organization. List organizations if the user did not
-   provide one.
+   provide one, and when several servers are connected use the one that returns
+   the target organization.
 3. Prefer MCP tools over manual API calls. The Probo MCP API mirrors the
    platform's GraphQL surface.
 

package/skills/open-source-compliance/references/workflows.md

@@ -1,23 +1,28 @@
 # Open-source compliance workflows
 
-This plugin wraps Probo's MCP API for Claude Code. Probo is a self-hostable
-GRC platform; its MCP server exposes tools for third parties, controls,
-obligations, risks, documents, audits, access reviews, and more.
+This plugin wraps Probo's MCP API. Probo is a self-hostable GRC platform; its
+MCP server exposes tools for third parties, controls, obligations, risks,
+documents, audits, access reviews, and more.
 
-## Authentication
+## Servers
 
-Probo MCP uses OAuth 2.0. Users sign in once via `/mcp` or
-`claude mcp login probo`; Claude Code stores and refreshes tokens
-automatically. Do not ask the user for API keys or bearer tokens for MCP
-access.
+The plugin ships the two hosted Probo instances. A self-hosted instance is
+added in the agent's own MCP configuration.
 
-| Variable | Purpose |
+| Server | Endpoint |
 | --- | --- |
-| `PROBO_BASE_URL` | Probo instance root URL (no trailing slash) |
+| `probo-us` | `https://us.probo.com/api/mcp/v1` |
+| `probo-eu` | `https://eu.probo.com/api/mcp/v1` |
+| self-hosted | `<instance-root>/api/mcp/v1` |
 
-MCP endpoint: `${PROBO_BASE_URL}/mcp/v1`
+## Authentication
+
+Probo MCP uses OAuth 2.0. Users sign in once per server via `/mcp` or
+`claude mcp login probo-us`; the agent stores and refreshes tokens
+automatically. Do not ask the user for API keys or bearer tokens for MCP
+access.
 
-OAuth discovery:
+OAuth discovery (on the instance root, not the MCP path):
 
 - Protected resource metadata: `/.well-known/oauth-protected-resource`
 - Authorization server metadata: `/.well-known/oauth-authorization-server`