WHEN HOTLINE
Choose Hotline when...
Use Hotline when the capability needs to be packaged, discovered, governed, and potentially monetized across teams or external agents.
Use Hotline
KEY TAKEAWAYS
In three lines
- MCP handles tool access; Hotline handles capability business shape.
- A Hotline can expose an MCP surface without collapsing into MCP.
- Marketplace, settlement, and operator identity live above the MCP layer.
DIMENSIONS
Dimension by dimension
Each row compares what Hotline standardizes, what MCP Server focuses on, and why the difference matters.
Dimension
Hotline
MCP Server
Primary job
Productize a capability for discovery, calling, and settlement.
Why it matters
This determines whether you are building a market-facing product or an internal runtime connector.
Expose tools to an agent runtime.
Identity
Responder identity is part of the operating model.
Why it matters
Trust and reputation need a stable seller-side identity.
Operator identity is outside the protocol.
Settlement
Per-call economics can live at the protocol layer.
Why it matters
A one-person company needs revenue mechanics, not just tool wiring.
Billing must be invented elsewhere.
Discovery
Hotlines are designed for public or team-level discovery.
Why it matters
Discovery is the difference between a capability catalog and a local integration file.
MCP servers are usually distributed by config or documentation.
WHEN MCP SERVER
Choose MCP Server when...
Use MCP alone when you only need a lightweight runtime tool surface and do not need seller identity, settlement, or marketplace behavior.
Not necessarily Hotline
PAGE FAQ
Common questions about MCP Server
Do I need to rewrite an existing MCP server to use Hotline?
No. The practical path is to wrap the existing implementation so the capability keeps its runtime surface while gaining a Hotline identity and packaging layer.
Can a Hotline still be consumed by MCP-friendly agents?
Yes. MCP can remain one of the access surfaces while the Hotline remains the canonical product and routing abstraction.
Why not stay at the MCP layer forever?
Because MCP does not answer marketplace discovery, operator identity, version governance, or settlement. Those become real product problems as soon as the capability leaves a local experiment.