API keys are issued per developer and map to one isolated Sourcefolio workspace. Store the key as a secret and send it on every MCP request.
Authorization: Bearer sfk_...
Keys are read-only by default. Workspace mutation requires a separately issued key containing the workspace:write permission.
Key lifecycle
Do not place keys in source control, URLs, or client logs.
Use separate keys for local development, CI, and each collaborator.
Ask your workspace administrator to revoke and replace a lost key.
Access administration
Each developer uses an individually issued credential connected to one workspace. Company-wide shared keys are not supported.
Workspace owners manage members, roles, and credential lifecycle through the workspace administration portal. These controls are intentionally outside MCP so connected tools cannot grant access or rotate credentials.
Tools
Examples show tool arguments and the JSON value returned inside MCP text content.
search_public_projects
Search verified npm, PyPI, Cargo, Maven, and Go projects by name or repository URL. Optionally restrict results to one ecosystem.
Set the workspace's official project state independently from individual recommendations. Valid values are evaluating, approved, rejected, and retired.