Azure DevOps remote MCP is GA: run it beside Sume's hosted MCP
Azure DevOps remote MCP went GA in sprint 278 with Foundry and Copilot Studio support. Here is how to hold it and Sume's MCP with separate credentials.
Yes, an agent can use the Azure DevOps remote MCP server and Sume's hosted MCP server side by side, as two separate remote servers with two separate credentials. Microsoft's sprint 278 release notes say the Azure DevOps Remote MCP Server is now generally available, with expanded support for Microsoft Foundry and Copilot Studio. Sume's endpoint is https://mcp.sume.com/mcp.
The Microsoft facts come from the sprint 278 release notes (read 2026-10-07). The Sume facts come from the MCP overview and OAuth page.
What each server gives the agent
The two servers do different work, so an agent that holds both can turn tracker data into media.
| Azure DevOps remote MCP | Sume hosted MCP | |
|---|---|---|
| Status | Generally available (sprint 278 notes) | Production endpoint, OAuth or API key |
| Reaches | Work items, repositories, pipelines | Account, catalog, jobs, assets, generation, crawl, Avatar tools |
| Hosted where | Microsoft, no local infrastructure | https://mcp.sume.com/mcp |
| Listed client surfaces | Foundry and Copilot Studio (expanded at GA) | Any remote MCP client; see the Foundry and Copilot Studio posts |
A tracker-to-video flow
A release-notes video is the obvious flow: the agent reads closed work items from Azure DevOps, drafts a script, and calls Sume to render it. Keep the paid step on its own rails.
- Connect Sume with OAuth and leave Write off while the agent only plans. Read tools such as
catalog_listandjobs_liststill work. - When you want the render, grant
mcp:write, callgeneration_admission_previewor senddry_run=true, then submit with anidempotency_keyandmax_spend_usd. - Wait with
jobs_waitin slices of 55 seconds or less and fetch results withjobs_result.
Keep credentials apart
Do not reuse tokens across servers. The Sume docs say an MCP OAuth token is not a Sume API key, and that you should not paste tokens into prompts or forward them to third parties. Azure DevOps has its own sign-in; give each server only the credential it issued.
Admin note
In a managed setup, an admin should list both URLs separately in the client's allowlist, so that approving one does not approve the other. If a Sume tool is missing, check the credential scope first with mcp_health and tools_list.
Sources
Related posts
More in Integrations
- BigQuery product table to Sume bulk queues and a queue map
Read active SKUs from BigQuery, cast columns to plain JSON types, create one Sume bulk queue per 100 rows, and stream queue id, index and SKU to a map table.
- Claude Code 2.1.290 claude -p skips resources/list: Sume is tools-only
Claude Code 2.1.290 no longer holds the first claude -p turn for HTTP MCP servers to answer resources/list. Sume declares tools only, so nothing is lost.
- Claude Code 2.1.293 HTTP MCP leak fix and long Sume job sessions
Claude Code 2.1.293 fixed a leak where an HTTP MCP connection kept every request it sent. Upgrade before a long Sume session and use batch jobs_wait.
- Claude Code MCP tool name over 128 characters: does Sume hit it?
Claude Code 2.1.292 leaves out an MCP tool whose name passes 128 characters and names it in an error. Sume's longest tool name is 36, so it never trips it.
Written by Sume