Repository navigation
feat(api): serve private skills over MCP to members of opted-in orgs - #192
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
visibilitydefaults toprivate, so the Skills extension only served skills someone had explicitly made public. Private skills are the main gap for paying teams.What changes
skills/list,skills/getandresources/read. This is the REST rule: any org member can read the org's skills.GET/PATCH /v1/orgs/{orgId}/mcp-policy, audited asmcp_policy.updated.Decisions to review
skills:readMCP scope is the better long-term control, but it depends on clients requesting it and existing connections signing in again.sk_keys stay anonymous on/mcp: CI can use the CLI withskills:read.apiKeyScope, so API keys can't turn this on.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
orgvisibility, immediate revocation, and a skill that goes private while listed in another org's project.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