MCP

The Warestack MCP lets an admin agent inspect the space and draft the pack against the live API. Share mcp.warestack.com . That host talks to https://api.warestack.com.

MCP URL: https://mcp.warestack.com/mcp

Use the same GitHub account as the console. Do not paste a token. Slack and Linear OAuth stay in the console; the MCP only reports whether they are connected.

Cursor

Open mcp.warestack.com and click Add to Cursor, or use this deeplink (Cursor must be installed):


cursor://anysphere.cursor-deeplink/mcp/install?name=warestack&config=eyJ1cmwiOiJodHRwczovL21jcC53YXJlc3RhY2suY29tL21jcCJ9

Or Settings → MCP → add a server named warestack with https://mcp.warestack.com/mcp. The first connection opens GitHub sign-in.

Claude

Customize → Connectors → Add custom connector. Paste https://mcp.warestack.com/mcp. Leave OAuth client ID and secret empty. Click Add, then Connect, then sign in with GitHub.

Claude Code:


claude mcp add --transport http warestack https://mcp.warestack.com/mcp

Codex


npx skills add https://mcp.warestack.com -g -a codex -y
codex mcp add warestack --url https://mcp.warestack.com/mcp
codex mcp login warestack

What it can do

Call space_status before recommending Slack, Linear, rules, or chains.

Tool	Effect
`list_spaces`	Spaces this token can open
`space_status`	Connections, teams, Slack and email addresses, and rules enabled on each repository
`list_attention`	Overview › Needs attention: For me and For the space
`list_metrics`	KPI summary, including repository and author breakdowns
`get_metric`	One analytics metric, including breakdown rows and the daily trend
`list_rules`	Catalog and custom rules, with enablement. Cite name and `rule_key`
`enable_rules`	Turn listed integer ids on for repositories that do not have them. Accepts confirmed parameter values; `block_merge` stays false. Do not pass `rule_key`
`disable_rules`	Turn listed rules off while preserving their saved configuration
`set_repositories`	Turn repository tracing on or off
`list_identities`	People, GitHub logins, and Slack-link state
`list_repository_roles`	Saved owner and other repository roles
`set_repository_owner`	Assign an individual repository owner
`list_slack_channels`	Channels in the connected Slack workspace
`add_slack_address`	Save a selected channel as a Warestack destination
`add_email_address`	Save email recipients as a destination. Recipients do not need a GitHub identity or space membership
`list_chains`	Automation chains
`list_chain_kinds`	Chain kinds that can be saved as drafts
`create_chain`	Save a catalog kind as a draft. `scheduled_report` accepts Slack and email destination ids
`set_chain_slack_destination`	Point a chain’s channel step at a saved Slack address
`enable_chain`	Enable a draft. GitHub-writing chains need a dry-run first
`pause_chain`	Stop new runs for an enabled chain
`list_reports`	Saved reports
`draft_report`	Start a custom report or execute a reviewed `report_definition_id`. Nothing is saved
`finish_report`	Confirm a proposed query or completed preview, then commit its server-owned draft revision
`schedule_report`	Create missing Slack/email addresses and save a `scheduled_report` draft for a saved report
`analyze_rule`	Draft a custom rule. Nothing is saved
`create_rule`	Save that draft as not enabled

analyze_rule and create_rule do not refresh a rule that already exists. Re-interpret and adopt that pin in the console. See Custom rule interpretations.

Reviewed report definition IDs are production_changes, failed_ci_jobs, changes_requested, review_bot_comments, urgent_issues_without_pr, stale_pull_requests, rule_violations, deployments_without_review_record, deployment_review_decisions, and repository_protection. When draft_report returns needs_confirmation, pass its confirmed query to finish_report. When it returns a completed preview, confirm that preview and pass its draft_revision as expected_revision. The tool sends the authenticated generation thread and revision—not generated SQL or rows—and can save a valid empty result. After save, schedule_report creates missing Slack channels and email addresses, then drafts a scheduled_report chain. Email can go to people who are not GitHub identities and are not in the space. A report that already has a scheduled_report chain is left unchanged. The new chain stays a draft until enable_chain. See Reports.

The live catalog is list_rules. Cite the name and rule_key that tool returns. enable_rules takes the integer id from that list, not the rule_key. If a rule needs configuration, ask for the values shown by list_rules or needs_configuration, then pass them in parameter_values_by_rule keyed by that integer id. Never invent values. Do not invent warestack.catalog or warestack.propose_pack. First enablement is the change-management pack. custom.* slugs are documented custom controls, not catalog rules.

create_chain and create_rule save drafts. Ask before enable_rules or enable_chain. Leave merge-blocking off. Trusted rule conclusions require complete outcomes for every persisted check; an incomplete merge-blocking evaluation fails closed. A reason-required acknowledgement is bound to the exact pull-request revision and finding. personal_digest is self-serve from Overview; do not create it. Do not infer a ticket link from raw PR text: Warestack can resolve known identifiers, but the MCP should report a link only when the API returns its persisted association.

list_attention exposes the current Overview queues, including surfaced rule-violation items. list_metrics and get_metric read the same KPI summary and analytics metrics as the console, including breakdowns. When both are present, review_comments_unresolved aliases actionable_review_threads; do not add them. Ask Warestack for those reads. Do not rebuild the queue or the numbers by listing pull requests, review requests, workflow runs, or deployments in the GitHub MCP. repo_github_id is a repository id from space_status. The MCP does not yet expose the complete evaluation history for an arbitrary pull request or an acknowledgement command; use the pull-request Events view for that evidence and action.

Skills

The same setup, ticket, and attention guides are published on the public MCP host. They do not add tools. Connect the MCP above as well, and sign in with the same GitHub account as the console. Discovery is https://mcp.warestack.com/.well-known/skills/index.json (and the agent-skills alias).


npx skills add https://mcp.warestack.com

Skills: warestack, warestack-setup, warestack-ticket-rules, warestack-attention. MCP prompts stay available for Claude Connectors.

Without this connection, stay on For AI agents and /catalog.json: propose only, and do not claim Warestack association-store facts.