Does your capability already exist as a CLI, API, or COM interface?
YesMake it discoverable (ODR, marketplace, docs).
NoBuild the CLI / API first. Then make it discoverable.
↓
Does this cross a boundary where you need centralized auth / policy / telemetry?
YesMCP (server, typically HTTP) is a good fit for org-scale governance.
NoPrefer a CLI + skill / prompt file. Avoid protocol overhead.
↓
Does your tool require persistent state across calls?
YesUse a session model (mcp-cli or similar). Keep the capability the focus.
NoStateless CLI is ideal. Simplest to ship and easiest for agents.
↓
Have you eval'd this with an actual agent on real tasks?
Yes, it helpsShip it.
No / unclearDon't ship until you have evidence.
If you're building an MCP server just to wrap a CLI or API that already works → Stop.
Ship the capability. Let the platform make it discoverable.