Skip to content

feat(api): serve private skills over MCP to members of opted-in orgs - #192

Merged
blakebauman merged 2 commits into
mainfrom
feat/mcp-private-skills
Nov 7, 2026
Merged

blakebauman merged 2 commits into
mainfrom
feat/mcp-private-skills

Conversation

@blakebauman

Copy link
Copy Markdown
Collaborator

Why

visibility defaults to private, so the Skills extension only served skills someone had explicitly made public. Private skills are the main gap for paying teams.

What changes

  • Access: a signed-in member can load their org's non-public, published skills through skills/list, skills/get and resources/read. This is the REST rule: any org member can read the org's skills.
  • Opt-in: new owner setting, Serve private skills over MCP, off by default, in Governance. GET/PATCH /v1/orgs/{orgId}/mcp-policy, audited as mcp_policy.updated.
  • Everyone else: anonymous callers, non-members and members of other orgs get the same answer as for a skill that doesn't exist.
  • Revocation: membership and the setting are read on every request, so turning it off or removing a member takes effect while a token is still valid.
  • Docs: new "Private skills" section on the MCP page.

Decisions to review

  • Off by default: MCP tokens have no skill scopes, so every client a member connects can read everything that member can. A skills:read MCP scope is the better long-term control, but it depends on clients requesting it and existing connections signing in again.
  • Per org, not per project: a private project keeps a skill out of a member's list, but any member can load it by URI, as in the console.
  • sk_ keys stay anonymous on /mcp: CI can use the CLI with skills:read.
  • Owner only: there is no admin role, and other policy edits are owner-only. The PATCH names no apiKeyScope, so API keys can't turn this on.
  • Own column: the policy PATCH routes replace their whole JSON object, so saving quotas could otherwise have changed this setting.

Rollout

The migration adds one column with a default of false. CI applies migrations before deploying the Worker, and the old Worker ignores the column. Behaviour is unchanged until an owner opts in.

Testing

  • New tests cover the switch being off, strangers, anonymous callers, members of other opted-in orgs, drafts, org visibility, immediate revocation, and a skill that goes private while listed in another org's project.
  • Route tests cover owner, editor, stranger, signed-out, and an API key holding every scope.
  • Breaking the gate or the route in six ways each failed a test: ignoring the opt-in, ignoring membership, showing everything, dropping the published check, opening the route to viewers, and letting owner-level keys through.
  • pnpm check, typecheck and tests pass across the workspace (499 API, 143 console), and the docs build.

Not tested: the console card hasn't been viewed in a browser, and no real MCP host has loaded a private skill.

🤖 Generated with Claude Code

blakebauman and others added 2 commits November 6, 2026 20:21
Skills default to private, so the MCP Skills extension couldn't serve most
of what a team actually publishes.

Members of an org can now load its private skills through an authenticated
MCP session, once an owner opts in. It is off by default because MCP tokens
have no skill scopes, so every client a member connects gets everything that
member can read. Anyone else gets the same answer as for a missing skill.

The switch is its own column because the policy PATCH routes replace their
whole JSON object, and it is console-only so an API key can't turn it on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@blakebauman
blakebauman merged commit 7565e9f into main Nov 7, 2026
8 checks passed
@blakebauman
blakebauman deleted the feat/mcp-private-skills branch November 7, 2026 03:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant