Back to browse
GitHub Repository

Service Catalog MCP -- Managing microservices by understanding the codebase

1 starsPython

Service-catalog-MCP – Index your codebase and make batch changes

by redbrandi·Jun 23, 2026·3 points·0 comments

AI Analysis

●●SolidSolve My ProblemSlick

Batch changes across repos via MCP when Sourcegraph only does search.

Strengths
  • Four-step workflow with confirmation gates: find, plan, diff, push.
  • Supports both Claude and Devin as CLI providers for code generation.
  • Self-hosted Docker setup with persistent volume for repo clones.
Weaknesses
  • MCP server space getting crowded with similar codebase tools.
  • Batch changes could be scripted manually with enough effort.
Target Audience

Engineering teams managing microservices

Similar To

Sourcegraph Cody · GitHub Copilot Workspace · ast-grep

Post Description

Hi all

3 things service catalog does:

* index *

It indexes the whole codebase, and per repo to make a sense of it. 2 types of indexing we are looking at, a codebase level where we let the agent figure out the relation between repositories and per repo, where we extract the data (libraries, dependencies, etc) with respect to what we know of the codebase

* search *

After indexing the whole codebase, we are able to run search. the search can be either lexical or logical. we pass the context of the codebase we generated in the index phase to the search and let search decide what to look for. User will be able to search by asking "find me repositories that are written with python, use library X and all the repos that are relevant to these repos".

* batch change *

Batch change lets users make changes in many services at the same time. So a user will be able to say "Find all repos with github actions job name X and update the version from 1 to 2". The mcp server will fire up claude code in clones targeted repositories, and make a change while passing the codebase and repostiories context to it for better decision making.

After making these changes, user can ask the server to make PRs, and check the PR status of them and give a summary

=================

You can find a video of me using the mcp server here: https://infraas.ai

Similar Projects

Developer Tools●●●Banger

Srclight – Deep code indexing MCP server (FTS5 and Tree-sitter)

Tree-sitter + FTS5 + MCP = tokens saved for AI agents to actually code, not search.

WizardryBig BrainZero to One
srclight
103mo ago
Developer Tools●●●Banger

I built a codebase analysis MCP: Stria

Indexes the Linux kernel in 80 seconds without AST parsers, where tree-sitter tools fail.

WizardryShip ItSolve My Problem
microbass
3122d ago
Developer Tools●●Solid

CasperAI – A local MCP server for cross-platform engineering context

It stitches Slack threads, PRs, tickets and docs into a local "context lake" and can point a mention like handlePayment() straight to the file and related PRs — very practical for debugging and postmortems. The use of SQLite FTS5 for local full-text search plus MCP for a unified context layer is a smart, pragmatic combo; success will hinge on connector reliability and search/ranking quality, not the README.

Niche GemSolve My Problem
chose166
114mo ago
AI/ML●●Solid

CocoIndex-Code open source embedded AST-based code MCP

AST-based code indexing saves tokens but Cursor and Continue already do this.

Solve My ProblemNiche Gem
georgehe9
213mo ago