Microservice.MD

Microservice.MD connects Claude to your microservice.md catalog, so it can work from your actual service designs instead of guessing from the code in one repo. Each service in your catalog has a MICROSERVICE.md spec and a set of generated files: OpenAPI, AsyncAPI, proto and GraphQL contracts, runbooks, ADRs, C4 diagrams and a context pack. Claude can read all of them, including the contracts of the services yours depends on, before it writes code that calls or consumes them. It also answers the question that matters before a breaking change: what else does this affect? Claude can look up which services publish or consume an event, and which services depend on a given service, including the endpoints they call when those are recorded. It then tells you which services and teams are involved. What you can do: - Implement a service from its spec and contracts - Call or consume another service using its real contract - Check the impact of changing an endpoint or event before you make the change - Find a service in your catalog, or resolve it from the Catalog ID line in a repo's MICROSERVICE.md Access is read-only. You sign in with OAuth, Claude sees only your own catalog, and it reads your last saved versions by default. If a service has unsaved edits, Claude tells you they aren't included. A microservice.md account is required.