Add MCP to Existing Services
You have a working go-micro service and want to make it accessible to AI agents via MCP. This guide covers the three approaches, from simplest to most flexible.
Migration Guides
Step-by-step guides for migrating to Go Micro from other frameworks.
Available Guides
- v5 to v6 - Upgrade to v6: new module path, TLS secure by default,
NewService - Add MCP to Existing Services - Make your services AI-accessible in 5 minutes
- From gRPC - Migrate from gRPC to Go Micro with minimal code changes
Coming Soon
We’re working on additional migration guides:
- From go-kit - Migrate from Go kit microservices framework
- From Standard Library - Upgrade from net/http and net/rpc
- From Gin/Echo - Transition from HTTP-only frameworks
- From Micro v3 - Upgrade from older Go Micro versions
Why Migrate to Go Micro?
- Pluggable Architecture - Swap components without changing code
- Zero Configuration - Works out of the box with sensible defaults
- Progressive Enhancement - Start simple, add complexity when needed
- Unified Abstractions - Registry, transport, broker, store all integrated
- Active Development - Regular updates and community support
Need Help?
- Check the Framework Comparison guide
- Review Architecture Decisions to understand design choices
- Ask questions in GitHub Discussions
- See the Contributing Guide to contribute new migration guides
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.