From sutro-dev-agents
Wire the local Sutro MCP server into the user’s editor — security bundle path, env vars, build steps for mcp/sutro.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sutro-dev-agents:sutro-mcp-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user needs to connect **Cursor**, **Claude Code**, or **VS Code** MCP clients to Sutro tooling.
Use this skill when the user needs to connect Cursor, Claude Code, or VS Code MCP clients to Sutro tooling.
~/.config/sutro/security-bundle). Do not commit the bundle; it contains private keys and JWTs.From the repo root:
cd mcp/sutro && npm install && npm run build
mcp/sutro/dist/index.js with node (see config/mcp.cursor-sample.json, config/mcp.vscode-sample.json, config/mcp.claude-sample.json).SUTRO_SECURITY_BUNDLE_DIR to the directory that contains ca.crt, mtls.crt, mtls.key, builder.jwt, and apiClient.id. Use an absolute path in MCP env if your client does not expand ~. A leading ~/ in the value is expanded by the server using $HOME.SUTRO_API_BASE (default https://sapi.withsutro.com).Use sutro_validate_bundle first to check local bundle readiness (required files + JWT refresh prerequisites), then run sutro_hello (calls GET /hello) to verify end-to-end connectivity.
When docs are unclear, treat live responses as the contract source of truth:
mcp/sutro, run npm run sutro-probe-shapes (uses mTLS + bundle bearer auth).--project-id=<uuid> to probe /projects/:id/applications for a specific project--timeout-ms=10000 to tune request timeout per endpoint--snapshot=./tmp/sutro-shapes.json to save a sanitized shape report for comparisonsmcp/sutro/src/ to match observed top-level shapes before trusting docs.npm test in mcp/sutro to verify normalizers and compatibility fallbacks.builder.jwt locally (optional)If the bundle’s builder.jwt expired but you still have a signing key (signing.pem preferred, fallback mtls.key) and the correct issuer + builder sub, you can mint a short-lived token without pasting passwords into chat:
mcp/sutro/.env.example to mcp/sutro/.env (never commit .env).SUTRO_SECURITY_BUNDLE_DIR, SUTRO_PROVISION_MODE=sign-only. Ensure jwtIssuer.id and either .sutro-builder-sid or builder.id (or SUTRO_BUILDER_SID) match what Sutro expects for iss / sub on the Builder JWT (How to secure connections).mcp/sutro: npm install then node --env-file=.env scripts/sutro-provision-from-env.mjs (or npm run sutro-provision with the same env loaded).For a full org init + new builder (only when your org can run /initialization), set SUTRO_PROVISION_MODE=full plus SUTRO_ORG_EMAIL, SUTRO_ORG_PASSWORD, SUTRO_COMMON_NAME, and SUTRO_JWT_ISSUER per the doc.
mcp/sutro/src/; keep tool names stable and extend rules/sutro.mdc when you add tools.sutro_list_projects and sutro_list_apps for discovery (includeScode=false by default for lighter payloads).sutro_pull_project_data or sutro_pull_app_for_edit when you need full SCode context before making changes.sutro_deploy_slang, or use sutro_apply_slang_changes for deploy + status verification (+ optional publish) in one call. For release workflows, publish options include versionType and replacePublishedVersion.sutro_apply_slang_from_file to avoid sending large inline payloads through tool arguments.npx claudepluginhub adrianjonmiller/sutro-mcp-server --plugin sutro-dev-agentsFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.