Service Atlas MCP Server
service-atlas/mcp
Exploração e governança de catálogo de serviços via MCP
Ver no GitHubServidor MCP que expõe ferramentas para explorar um Service Atlas API, permitindo navegação de times, listagem de serviços, busca por nome, rastreamento de dependências, análise de débito técnico e histórico de releases. Integra-se nativamente com Claude para consultas sobre arquitetura e governança de serviços.
Instalação
npx convez-ai service-atlas/mcp1 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
- Mapear dependências entre microserviços e analisar impacto de mudanças
- Consultar débito técnico e priorizar refatorações
- Localizar proprietários de serviços e responsabilidades de times
- Gerar relatórios de risco e análise de arquitetura
- Rastrear releases e histórico de mudanças por período
Veredito

MCP bem estruturado para governança de serviços em organizações com catálogo centralizado. Oferece cobertura completa (busca, dependências, risco, débito) mas requer acesso prévio a uma instância rodando do Service Atlas; útil em contextos enterprise com arquitetura distribuída.
README
A tradução para o português deste README ainda está na fila.
Service Atlas MCP Server
Purpose
This MCP server exposes tools and resources for exploring a Service Atlas API: browsing teams, listing services for a team, searching services by name, seeing which teams own a service, and exploring service dependencies, tech debt, and releases.
Capabilities
-
Prompts that guide the AI on how to complete common tasks using the tools/resources
get_servicesget_all_teamsget_services_by_teamfind_service_by_namefind_which_team_owns_a_serviceget_debtget_releasesget_service_dependencies_and_dependentsget_service_riskanalyze_service_risk_and_impact
-
Tools
get_services(page)→ GET/services(25 items per page)get_all_teams()→ GET/teams(auto-paginates up to 200 results)get_services_by_team(team_id)→ GET/teams/{team_id}/servicesfind_service_by_name(query)→ GET/services/search?query={query}get_teams_by_service(service_id)→ GET/services/{service_id}/teamsget_debt()→ GET/reports/services/debtget_debts_for_service(service_id)→ GET/services/{service_id}/debtcreate_debt(service_id, title, description, debt_type)→ POST/services/{service_id}/debtget_releases(start, end)→ GET/releases/{start}/{end}get_service_dependencies(service_id)→ GET/services/{service_id}/dependenciesget_service_dependents(service_id)→ GET/services/{service_id}/dependentscreate_dependency(service_id, dependency_id, version)→ POST/services/{service_id}/dependencyget_service_risk(service_id)→ GET/reports/services/{service_id}/riskget_service_types()→ GET/services/typescreate_service(name, description, service_type, url, tier)→ POST/servicesupdate_service(service_id, name, description, service_type, url, tier)→ PUT/services/{service_id}remove_dependency()→ Instructs user to use web interfaceget_version()→ Returns the MCP server versionget_website()→ Retrieves the Service Atlas website URL
-
Resources (MCP resources namespace)
serviceatlas://teams→ All teamsserviceatlas://services?page={page}→ Paginated servicesserviceatlas://teams/{team_id}/services→ Services by teamserviceatlas://services/search/{query}→ Search services by nameserviceatlas://services/{service_id}/teams→ Teams by serviceserviceatlas://debts→ Debt reportserviceatlas://debts/{service_id}→ Debts by serviceserviceatlas://releases/{start}/{end}→ Releases in date rangeserviceatlas://services/{service_id}/dependencies→ Service dependenciesserviceatlas://services/{service_id}/dependents→ Service dependentsserviceatlas://services/{service_id}/risk→ Service risk reportserviceatlas://services/types→ Service types
Resource Scheme
Resources use the serviceatlas:// scheme so that requests are routed specifically to this server.
Use Cases
Each use case is implemented with a prompt, a tool, and an equivalent resource.
- List all services (paginated) → tool
get_servicesor resourceserviceatlas://services?page={page} - List all teams → tool
get_all_teamsor resourceserviceatlas://teams - List all services that belong to a team → tool
get_services_by_teamor resourceserviceatlas://teams/{team_id}/services - Find a service by name → tool
find_service_by_nameor resourceserviceatlas://services/search/{query} - Find which team owns a service → tool
get_teams_by_serviceor resourceserviceatlas://services/{service_id}/teams - Get tech debt report → tool
get_debtor resourceserviceatlas://debts - Get tech debt for a service → tool
get_debts_for_serviceor resourceserviceatlas://debts/{service_id} - Create tech debt → tool
create_debt - Get releases in a date range → tool
get_releasesor resourceserviceatlas://releases/{start}/{end} - Get service dependencies → tool
get_service_dependenciesor resourceserviceatlas://services/{service_id}/dependencies - Get service dependents → tool
get_service_dependentsor resourceserviceatlas://services/{service_id}/dependents - Create a service dependency → tool
create_dependency - Remove a service dependency → tool
remove_dependency - Get service risk report → tool
get_service_riskor resourceserviceatlas://services/{service_id}/risk. This report is used to answer the question: "If this service changes or fails, how broadly could that impact the system?" It provides a heuristic score based on the service's position in the dependency graph. - List service types → tool
get_service_typesor resourceserviceatlas://services/types - Create a new service → tool
create_service - Update an existing service → tool
update_service - Get MCP version → tool
get_version - Get website URL → tool
get_website
Running and Testing Locally
Use the Model Context Protocol Inspector to connect and test this MCP server.
Prereqs: Node.js installed.
- Start the Inspector from the project root:
npx @modelcontextprotocol/inspector
- In the Inspector UI, add a new Server with:
- Command:
uv - Args:
run src/mcp_server.py - Environment:
API_URL→ base URL of your Service Atlas API (e.g.http://localhost:8080)
- Connect to the server from the Inspector and try the tools/resources listed above.
If you run a local Service Atlas API for testing, make sure it’s reachable at the URL you put into API_URL.
References
- MCP Resources: https://modelcontextprotocol.io/specification/2025-06-18/server/resources
- FastMCP Docs: https://gofastmcp.com/getting-started/welcome