WHEN HOTLINE
Choose Hotline when...
When the capability needs to be productized — identity, per-call settlement, version management, and public ratings; or when agent teams need a discoverable, subscribable capability distribution layer.
Use Hotline
KEY TAKEAWAYS
In three lines
- MCP solves tool access; Hotline solves capability productization — they complement each other.
- A Hotline can expose an MCP surface; product routing and settlement happen at the Hotline layer.
- Identity, discovery, versioning, ratings, and settlement typically need a product layer above MCP — Hotline provides that 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
Package a capability for discovery, calling, and settlement.
Why it matters
One focuses on product shape, the other on runtime plumbing — different problems.
Connect tools to an agent runtime.
Identity & trust
Protocol-level responder identity supports ratings and trust evaluation.
Why it matters
Capabilities going to market need seller-side identity; MCP focuses elsewhere.
Great for agent-runtime tool access; identity, discovery, ratings, and settlement are typically handled by a product layer above.
Settlement
Per-call settlement at the protocol layer.
Why it matters
Capabilities that need direct monetization require protocol-level settlement.
Focused on tool invocation plumbing; billing logic is left to the product layer above.
Discovery
Designed for public or team-level discovery via Marketplace.
Why it matters
Discovery is what turns a local integration into a capability catalog.
Distributed by agent config or documentation; discovery model is up to the consumer.
WHEN MCP SERVER
Choose MCP Server when...
When you only need runtime tool access without product packaging (discovery, settlement, ratings). MCP is clean and efficient at the tool-access layer.
Not necessarily Hotline
PAGE FAQ
Common questions about MCP Server
Do I need to rewrite an existing MCP server to use Hotline?
No. A wrapper lets the existing implementation keep its runtime surface while gaining Hotline's identity, billing, versioning, and ratings layer.
Can a Hotline still be consumed by MCP-friendly agents?
Yes. MCP can remain one of the access surfaces while the Hotline stays the canonical product and routing abstraction.
When does MCP alone make more sense?
When you only need a lightweight runtime tool surface and don't need seller identity, settlement, or marketplace behavior. MCP is purpose-built for that job.