Open Agent Tools - MCP Servers para Gestão de Projetos
pragmaticagile/open-agent-tools
MCP servers para Jira/Azure DevOps com foco em workflows de entrega
Ver no GitHubRepositório com MCP servers e skills prontos para agentes trabalhar com Jira e Azure DevOps de forma segura e prática. Inclui connectors para leitura e escrita de trabalho, sprints, pipelines e relatórios de entrega, além de templates para criar novos servers.
Instalação
npx convez-ai pragmaticagile/open-agent-tools1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Sincronizar status de sprints e work items com assistentes de IA
- Gerar relatórios de risco e itens bloqueados automaticamente
- Conectar pipelines e dashboards do Azure DevOps a agentes Claude
- Implementar workflows de escrita segura em ferramentas de gestão
Veredito

Solução madura e bem arquitetada para times de engenharia que precisam de agentes IA conectados a ferramentas de gestão. Destaca-se pelo foco em segurança, read-first design e workflows de entrega reais, não apenas leitura de dados.
README
A tradução para o português deste README ainda está na fila.
Pragmatic Agile Open Agent Tools
Public MCP servers, agent skills, templates, and guides for practical delivery work.
This repository is a public home for tools that help AI clients such as Codex, Claude, VS Code, Cursor, and other MCP-compatible apps work with engineering and delivery systems. Each package is documented and testable on its own, while the repo keeps one consistent structure for future MCPs and skills.
Start Here
- MCP server catalog
- Jira Plus MCP
- Azure DevOps Plus MCP
- Skills catalog
- ADO Delivery Management skill
- Publishing checklist
- Security guidance
- Contributing guide
Featured MCP Servers
| Tool | What It Helps With | Status |
|---|---|---|
| jira-plus-mcp | Jira Cloud projects, issues, boards, sprints, reports, Plans/Roadmaps read access, and optional write workflows | Ready |
| ado-plus-mcp | Azure DevOps projects, teams, boards, sprints, bugs, repos, pipelines, test plans, dashboards, and delivery reports | Ready |
Repository Layout
/
README.md
CONTRIBUTING.md
SECURITY.md
docs/
index.md
mcp-servers.md
publishing-checklist.md
mcp-servers/
README.md
ado-plus-mcp/
jira-plus-mcp/
skills/
README.md
templates/
mcp-server/
skill/
User Promise
These tools are designed to be:
- Simple to install for non-specialist users.
- Read-first and safe by default.
- Explicit about write mode and permissions.
- Friendly when a connected service blocks access.
- Free of hardcoded personal, company, project, token, or local machine values.
Why This Is Different
Most agent connectors stop at "let the assistant read a tool." This repo is focused on what teams need after connection: safer setup, delivery-ready reports, role-aware summaries, and clear next actions.
The goal is to help teams answer everyday questions faster:
- What changed yesterday?
- What is at risk today?
- Who needs help or a decision?
- Which work is aging, blocked, unowned, or missing estimates?
- Are sprint, roadmap, pipeline, test, and dashboard signals visible enough to trust?
The MCP servers provide the read-only connection. The skills turn that data into practical delivery management workflows.
Public Safety Rules
Before adding or publishing anything:
- Do not commit
.envfiles. - Do not commit PATs, API keys, tokens, cookies, certificates, or credentials.
- Do not commit local MCP client config files.
- Do not commit private organization, project, team, repo, sprint, work item, or customer data.
- Use placeholders such as
YOUR_ORGANIZATION_NAME_HERE,YOUR_PROJECT_NAME_HERE,YOUR_EMAIL_HERE, andYOUR_API_TOKEN_HERE. - Run the publishing checklist in docs/publishing-checklist.md.
Working With A Package
Each MCP server is managed from its own folder.
cd mcp-servers/jira-plus-mcp
npm install
npm run build
npm test
npm pack --dry-run
Review package contents carefully before publishing to GitHub or npm.