docs(mcp): document well-known managed integration ids - #599
Conversation
Warp now accepts short managed-integration ids (linear, slack, jira) wherever an MCP server UUID is accepted: bare `--mcp` arguments and `warp_id` values in cloud agent MCP configs. This shipped with the WellKnownMcpIds flag going GA. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment |
|
Your GitHub account is not connected to Warp. Connect it here. |
|
I ran into an unexpected error while working on this. You can view the conversation on Warp. Powered by Oz |
The linear/slack/jira managed integration ids only resolve for runs executing inside a Warp Factory (jira also resolves for a Jira-triggered run). A plain oz agent run / run-cloud invocation silently skips the server, so document that restriction next to the example instead of implying it always works. Co-Authored-By: Warp <agent@warp.dev>
![warp-agent-staging[bot]](https://avatars.githubusercontent.com/in/2196476?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR documents well-known Warp-managed integration IDs and now accurately limits linear and slack resolution to eligible Factory runs while preserving the Jira-event exception. The documentation change passes the correctness and style review, but the PR description needs a current-state rewrite.
Concerns
💡 [SUGGESTION] Rewrite the PR description as a clean current-state summary. Remove the audit provenance, rework chronicle, source-code evidence, and unrelated deferred findings so reviewers can evaluate the documentation change without process or unrelated scope noise.
Verdict
Checks: build ✅ · tests n/a (documentation-only; no repository presubmit or test command) · CI ✅ · visual proof n/a
Found: 0 critical, 0 important, 1 suggestion
Request changes
Review run
https://oz.staging.warp.dev/runs/01a03071-ca3c-7439-ba50-7f4c0cec3ba4
There was a problem hiding this comment.
Overview
This re-review confirms the managed-integration ID documentation accurately describes the Factory and Jira-triggered-run resolution restrictions. The PR description is now a clean current-state summary of the shipped documentation change.
Verdict
Checks: build ✅ · tests n/a (documentation-only) · CI ✅ · style lint ✅ · internal links ✅ · visual proof n/a
Found: 0 critical, 0 important, 0 suggestions
Approve
Review run
https://oz.staging.warp.dev/runs/01a03094-4bf7-7ad0-b2a2-b1cc6b2a7906
2 participants
Summary
Warp accepts short managed integration ids wherever an MCP server UUID is accepted, so agents can reach the Warp-hosted Linear, Slack, and Jira MCP servers without looking up a UUID. This was previously undocumented.
Changes
reference/cli/mcp-servers.mdx— the--mcpflag now documents four formats and gains a Passing Warp-managed integration servers by id section with an example, the recognized ids (linear,slack,jira), and a caution noting thatlinear/slackresolve only inside a Warp Factory run andjiraalso resolves for a Jira-triggered run.platform/mcp.mdx— thewarp_idfield description and the Requirements and defaults section now document the same managed integration ids and resolution scope.Verification
npm run buildpasses.style_lint --changedreports no issues.