Audience 01
Developers
Needs the same permission model for people and agents.
Agents, MCP & capabilities · Concept
Where the work actually changes.
CustomMCP is aimed at Developers, SaaS companies, enterprises, automation agencies.
01
Who it is for
Three audiences, one boundary model.
Audience 02
SaaS companies
Uses the product where the cost of an unscoped action is higher than the cost of setup.
Audience 03
enterprises
Needs the same permission model for people and agents.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Visual and programmatic MCP generation | Removes an ad hoc step from the workflow. | Specified |
| Tool, resource and prompt definitions | Makes an existing action reviewable. | Specified |
| Authentication and authorization | Removes an ad hoc step from the workflow. | Specified |
| Testing, deployment and observability | Removes an ad hoc step from the workflow. | Specified |
| SDK, CLI, API and commercial publishing | Removes an ad hoc step from the workflow. | Specified |
03
Migration
How a team would move from the status quo without a big-bang cutover.
Step 01
Map the current path
Name the tools, owners and handoffs that the product replaces. Nothing is removed yet.
Step 02
Run one capability
Pick a single scoped capability and run it alongside the old path, with evidence compared side by side.
Step 03
Retire the old path
Remove the previous tool only when the new record is complete enough to audit.