Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Azure DevOps (BYOK) icon

Azure DevOps (BYOK)

Read your Azure DevOps projects, repositories, pull requests, commits, branches, builds and work items with BYOK

Unify Dynamics LLC

Documentation
Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderAzure DevOpsunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What Azure DevOps projects are in the fabrikam organization?
Tools called
list_projects
What Git repositories are in the Azure DevOps project SampleProject?
Tools called
list_repositories
Which pull requests are active in Azure DevOps repository SampleRepository?
Tools called
list_pull_requests
What were the latest commits in Azure DevOps repository SampleRepository?
Tools called
list_commits
What branches does Azure DevOps repository SampleRepository have?
Tools called
list_refs
Did the latest Azure DevOps builds in SampleProject succeed?
Tools called
list_builds

About

Azure DevOps (BYOK) lets an AI assistant read your own Azure DevOps data through the Azure DevOps API with a key you supply (personal access token). Read-only: 9 tools (list_projects, list_repositories, list_pull_requests, list_commits, list_refs, list_builds, list_build_definitions, query_work_items, get_work_items). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to dev.azure.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure DevOps. Azure DevOps and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Azure DevOps API (dev.azure.com) with a BYOK key; documentation: https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-7.1. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List projectsList the projects of an organization with name, id, description, visibility, state and last update.
  • List repositoriesList the Git repositories of a project with name, id, default branch, size, disabled and fork flags and web link.
  • List pull requestsList pull requests of a repository (active by default) with title, status, creator name, branches, draft flag and merge status.
  • List commitsList commits of a repository (newest first) with commit id, message, author name and date; filter by branch, path, author or dates.
  • List refsList branches and tags of a repository with full ref name and the commit id they point to; use filter 'heads/' for branches or 'tags/' for tags.
  • List buildsList pipeline builds with number, status, result, branch, definition name, times and who requested it; filter by definition, branch, status or result.
  • List build definitionsList pipeline (build definition) names, ids, folder paths and queue status of a project.
  • Query work itemsRun a WIQL query and return the matching work item ids and links (use get_work_items for their details), for example "SELECT [System.Id] FROM…
  • Get work itemsGet up to 200 work items by id with the chosen fields (title, type, state, iteration, dates by default).

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-azuredevops.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-azuredevops.connectorbay.com/mcp
RESTPOST https://byok-azuredevops.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-azuredevops.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your personal access token in the X-Upstream-Key header (get one at learn.microsoft.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Azure DevOps connector: questions and answers

What is the Azure DevOps connector?

Azure DevOps (BYOK) lets an AI assistant read your own Azure DevOps data through the Azure DevOps API with a key you supply (personal access token). It is a hosted MCP server with 9 tools such as List projects, List repositories, List pull requests, List commits, List refs, List builds, published by Unify Dynamics LLC. It is independent and not affiliated with Azure DevOps.

How do I connect Azure DevOps to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-azuredevops.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-azuredevops.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-azuredevops.json.

Do I need a Azure DevOps account or API key?

Yes: this is a bring-your-own-key connector. Create a personal access token at https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Azure DevOps read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Azure DevOps connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Parallel (BYOK)

Read your Parallel web research monitors and their change events, task runs and task groups with your own API key

Live · MCP + REST6 tools

Parasail (BYOK)

Read your Parasail model list, invoices, spend breakdowns and dedicated deployment status with your own API key

Live · MCP + REST7 tools

Paris Open Data (BYOK)

Browse and query the open datasets of the City of Paris open data portal (Opendatasoft Explore API) with your own portal API key

Live · MCP + REST7 tools

Particle (BYOK)

Read your Particle IoT devices, their online status and firmware, and product fleets with BYOK

Live · MCP + REST4 tools

Particle (BYOK)

Read your Particle IoT devices and cloud variables, call a device function and flash a device LED to find it, with your own access token

Live · MCP + REST4 tools

Particle Libraries (BYOK)

Browse the Particle firmware library catalog and the firmware build targets (Device OS versions per platform) with your own access token

Live · MCP + REST5 tools

Documentation

Back to top

Azure DevOps (BYOK) — connector documentation

  • MCP endpoint: https://byok-azuredevops.connectorbay.com/mcp
  • REST API: POST https://byok-azuredevops.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-azuredevops.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Azure DevOps personal access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-azuredevops.connectorbay.com/health · Tool schemas: https://byok-azuredevops.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-azuredevops · agent@connectorbay.com

What Azure DevOps (BYOK) is for

Azure DevOps (BYOK) lets an AI assistant read your own Azure DevOps data through the Azure DevOps API with a key you supply (personal access token). Read-only: 9 tools (list_projects, list_repositories, list_pull_requests, list_commits, list_refs, list_builds, list_build_definitions, query_work_items, get_work_items). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to dev.azure.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure DevOps. Azure DevOps and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What Azure DevOps projects are in the fabrikam organization?"
  • "What Git repositories are in the Azure DevOps project SampleProject?"
  • "Which pull requests are active in Azure DevOps repository SampleRepository?"
  • "What were the latest commits in Azure DevOps repository SampleRepository?"
  • "What branches does Azure DevOps repository SampleRepository have?"
  • "Did the latest Azure DevOps builds in SampleProject succeed?"

What it does

  • list_projects: List the projects of an organization with name, id, description, visibility, state and last update.
  • list_repositories: List the Git repositories of a project with name, id, default branch, size, disabled and fork flags and web link.
  • list_pull_requests: List pull requests of a repository (active by default) with title, status, creator name, branches, draft flag and merge status.
  • list_commits: List commits of a repository (newest first) with commit id, message, author name and date; filter by branch, path, author or dates.
  • list_refs: List branches and tags of a repository with full ref name and the commit id they point to; use filter 'heads/' for branches or 'tags/' for tags.
  • list_builds: List pipeline builds with number, status, result, branch, definition name, times and who requested it; filter by definition, branch, status or result.
  • list_build_definitions: List pipeline (build definition) names, ids, folder paths and queue status of a project.
  • query_work_items: Run a WIQL query and return the matching work item ids and links (use get_work_items for their details), for example "SELECT [System.Id] FROM WorkItems WHERE [System.State] = 'Active'".
  • get_work_items: Get up to 200 work items by id with the chosen fields (title, type, state, iteration, dates by default).

BYOK key

You bring your own Azure DevOps personal access token (https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to dev.azure.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Azure DevOps API (dev.azure.com) with a BYOK key; documentation: https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-7.1. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure DevOps. Azure DevOps and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Azure DevOps account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Azure DevOps (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Azure DevOps (BYOK) is. Azure DevOps (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Azure DevOps data: Read your Azure DevOps projects, repositories, pull requests, commits, branches, builds and work items with BYOK. You bring your own Azure DevOps personal access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Azure DevOps call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to dev.azure.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Azure DevOps rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Azure DevOps receives. The request we make on your behalf, including the key and the arguments, under Azure DevOps's own terms and privacy policy. Azure DevOps acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Azure DevOps gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Azure DevOps data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Azure DevOps (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Azure DevOps at any time to end all access.

Children. Azure DevOps (BYOK) is a general-audience service operated by the adult using the assistant, under Azure DevOps's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Azure DevOps (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Azure DevOps (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Azure DevOps (BYOK) provides: Read your Azure DevOps projects, repositories, pull requests, commits, branches, builds and work items with BYOK. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Azure DevOps credentials and only access data you are allowed to access. Azure DevOps's terms apply to your use of Azure DevOps; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Azure DevOps. Azure DevOps and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Azure DevOps returns, lightly trimmed; it may be incomplete, delayed or changed by Azure DevOps. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Azure DevOps account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Azure DevOps's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Azure DevOps may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Azure DevOps key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Azure DevOps takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-azuredevops

Support

Back to top

Azure DevOps (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Azure DevOps (BYOK) never asks for them.

Get Azure DevOps (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Azure DevOps personal access token. Create one at https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Azure DevOps. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Azure DevOps.