Asim Aslam
c7657f73f4
* test(harness): read agent plan from the scoped store
The store-scoping change moved an agent's plan from the default table
key agent/{name}/plan to its own table (database "agent", table {name},
key "plan"). The plan-delegate harness tests still read the old key and
failed with 'not found'; read through store.Scope(mem, "agent", name)
like the agent does.
* docs: orient agents-first across README, landing, and docs overview
Lead with agents (then services and flows), surface MCP + A2A as the
interop story, and frame agents as services. Landing hero and feature
grid reordered agents-first with an A2A gateway card.
* v6: module path go-micro.dev/v6, TLS secure by default, NewService
Cut v6. Three breaking changes, bundled so the major bump is paid once:
- Module path go-micro.dev/v5 -> go-micro.dev/v6 across all imports + go.mod.
- TLS verification on by default (was off). MICRO_TLS_SECURE removed;
MICRO_TLS_INSECURE=true opts out for self-signed/dev.
- micro.NewService(name, opts...) is the canonical service constructor,
symmetric with NewAgent/NewFlow; micro.New kept as a deprecated alias;
the old name-less NewService(opts...) removed. Generators emit NewService.
Also ports the JWT auth token provider in-module (go-micro.dev/v6/auth/jwt/token
on golang-jwt/jwt/v5), dropping the v5-pinned github.com/micro/plugins/v5/auth/jwt
and the deprecated dgrijalva/jwt-go.
Docs/README/landing updated to v6 and @latest; v5->v6 migration guide added;
CHANGELOG cut as [6.0.0]. Blog posts left at their historical versions.
---------
Co-authored-by: Claude <noreply@anthropic.com>
Platform Example: AI Agents Meet Real Microservices
This example mirrors the micro/blog platform — a real microblogging application built on Go Micro. It demonstrates how existing microservices become AI-accessible through MCP with zero changes to business logic.
Services
| Service | Endpoints | Description |
|---|---|---|
| Users | Signup, Login, GetProfile, UpdateStatus, List | Account management and authentication |
| Posts | Create, Read, Update, Delete, List, TagPost, UntagPost, ListTags | Blog posts with markdown and tagging |
| Comments | Create, List, Delete | Threaded comments on posts |
| Send, Read | Internal messaging between users |
Running
go run .
MCP tools available at: http://localhost:3001/mcp/tools
Agent Scenarios
These are realistic multi-step workflows an AI agent can complete:
1. New User Onboarding
"Sign up a new user called carol, then write a welcome post introducing herself"
The agent will: call Signup → use the returned user ID → call Posts.Create
2. Content Creation
"Log in as alice and write a blog post about Go concurrency patterns, then tag it with 'golang' and 'concurrency'"
The agent will: call Login → call Posts.Create → call TagPost twice
3. Social Interaction
"List all posts, find the welcome post, and comment on it as bob saying 'Great to be here!'"
The agent will: call Posts.List → pick the right post → call Comments.Create
4. Cross-Service Workflow
"Send a mail from alice to bob welcoming him, then check bob's inbox to confirm delivery"
The agent will: call Mail.Send → call Mail.Read to verify
5. Platform Overview
"Show me all users, all posts, and all tags currently in use"
The agent will: call Users.List, Posts.List, and ListTags (potentially in parallel)
How It Works
The key insight: you don't need to write any agent-specific code. The MCP gateway discovers services from the registry, extracts tool schemas from Go types, and generates descriptions from doc comments.
service := micro.NewService("platform",
micro.Address(":9090"),
mcp.WithMCP(":3001"), // This one line makes everything AI-accessible
)
service.Handle(&Users{})
service.Handle(&Posts{})
service.Handle(&Comments{})
service.Handle(&Mail{})
Each handler method becomes an MCP tool. The @example tags in doc comments give agents sample inputs to learn from.
Connecting to Claude Code
Add to your Claude Code MCP config:
{
"mcpServers": {
"platform": {
"command": "curl",
"args": ["-s", "http://localhost:3001/mcp/tools"]
}
}
}
Or use stdio transport:
micro mcp serve --registry mdns
Architecture
Agent (Claude, GPT, etc.)
│
▼
MCP Gateway (:3001) ← Discovers services, generates tools
│
▼
Go Micro RPC (:9090) ← Standard service mesh
│
├── UserService ← Signup, Login, Profile
├── PostService ← CRUD + Tags
├── CommentService ← Threaded comments
└── MailService ← Internal messaging
Relation to micro/blog
This example is a simplified, self-contained version of micro/blog. The real platform splits each service into its own binary with protobuf definitions. This example uses Go structs directly for simplicity, but the MCP integration works identically either way — the gateway discovers services from the registry regardless of how they're implemented.