Aigist vs Azure DevOps (ADO)
A side-by-side look at the Aigist and Azure DevOps (ADO) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Azure DevOps (ADO)Developer Tools · Local subprocess (stdio)The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.55GoodAuth: not declaredVerdict: choose Aigist for developer tools work over a hosted endpoint; choose Azure DevOps (ADO) for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aigist when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
publish, list_pages, get_page.
AChoose Azure DevOps (ADO) when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Azure DevOps (ADO) | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 47/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,067 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Aigist | View Azure DevOps (ADO) |
Tools & capabilities
Aigist tools 5
publishPublish an HTML/Markdown page and get a shareable URLlist_pagesList your published pagesget_pageRetrieve the source of one of your pagesupdate_pageUpdate one of your pages in place (same URL)delete_pageDelete one of your pages
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aigist
{
"mcpServers": {
"aigist": {
"url": "https://ai-gist.com/mcp"
}
}
}
Azure DevOps (ADO)
{
"mcpServers": {
"azure-devops-ado": {
"command": "npx",
"args": [
"-y",
"@azure-devops/mcp"
]
}
}
}
Frequently asked questions
Aigist is categorized under Developer Tools and uses a remote HTTP/SSE transport. Azure DevOps (ADO) belongs to Developer Tools and uses a local stdio subprocess. Pick Aigist for developer tools work and Azure DevOps (ADO) for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Aigist has no declared pricing — check the project's own site. Azure DevOps (ADO) is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aigist and azure-devops-ado as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aigist has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,067 GitHub stars.