Agentic SDLC governance and security controls for AI coding agents working with GitHub.
If you already use Agentic SDLC MCP, the agentic sdlc mcp mcp server is the piece that lets your assistant work with it directly. Agentic SDLC governance and security controls for AI coding agents working with GitHub.
Governance and evidence controls for AI coding agents working in real GitHub repositories.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
repo_context — An agent needs repository facts before planningplan_from_context — A goal needs an SDLC plan and issue draftsprepare_work_item — An agent is about to implement a GitHub Issuecreate_issue_set — A reviewed plan should become GitHub Issuescreate_pr_summary — A pull request needs a reviewable overviewquality_gate_status — A team needs real merge-gate evidencereview_pr_against_standard — A pull request needs SDLC and security reviewbranch_protection_status — A team needs branch and ruleset visibilityworkflow_permissions_audit — GitHub Actions token permissions need reviewsecurity_triage — Release or incident work needs GitHub security alertsrelease_readiness_check — A human is deciding whether to publishagent_handoff_packet — Another agent must continue the workConfiguration is passed through the environment: GITHUB_TOKEN, GITHUB_OWNER, GITHUB_REPO. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at agentic-sdlc-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Agentic SDLC MCP's toolset — repo_context, plan_from_context, prepare_work_item and 10 more — is a fair guide to whether it matches your workflow. It is maintained by SakuraCianna; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| repo_context | An agent needs repository facts before planning |
| plan_from_context | A goal needs an SDLC plan and issue drafts |
| prepare_work_item | An agent is about to implement a GitHub Issue |
| create_issue_set | A reviewed plan should become GitHub Issues |
| create_pr_summary | A pull request needs a reviewable overview |
| quality_gate_status | A team needs real merge-gate evidence |
| review_pr_against_standard | A pull request needs SDLC and security review |
| branch_protection_status | A team needs branch and ruleset visibility |
| workflow_permissions_audit | GitHub Actions token permissions need review |
| security_triage | Release or incident work needs GitHub security alerts |
| release_readiness_check | A human is deciding whether to publish |
| agent_handoff_packet | Another agent must continue the work |
| sdlc_evidence_packet | A workflow decision needs a portable evidence snapshot |
{
"mcpServers": {
"agentic-sdlc": {
"command": "npx",
"args": ["-y", "agentic-sdlc-mcp"],
"env": {
"GITHUB_TOKEN": "your-value",
"GITHUB_OWNER": "your-value",
"GITHUB_REPO": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GITHUB_TOKEN | Credential the server authenticates with. | Yes |
| GITHUB_OWNER | Configuration value read at startup. | Optional |
| GITHUB_REPO | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.