eCommerce
openintentprotocol.com
An MCP server for finding local business offers, holding slots, and confirming, canceling, or checking bookings.
ENDPOINT 1
https://openintentprotocol.com/mcp
MCP server metadata
- Name
- intent-hub
- Version
- 0.1.0
Booking runs in one order: find_offers turns the person's sentence into offers, hold_slot reserves the slot of one bid for ten minutes, confirm_booking books it with a name and a phone number. If find_offers answers `complete: false`, put its `question` to the person and call find_offers again with the same `session` and their answer as `text`. Every answer carries a `session` id: pass it back into every later call, because it is the only thing that ties the conversation, the bids and the holds together. Reading is open to anyone, but hold_slot, confirm_booking, cancel_booking need an identity: call register_agent once, keep the key it answers (it is shown once) and send it as `Authorization: Bearer <key>` on every later call.
Known tools 10
hold_slotHold the slot of one bid from this session's round for ten minutes, before asking the person for their details.
Inferred read-onlyconfirm_bookingConfirm a held slot with the customer's name and phone number; this is the booking.
Inferred read-onlycancel_bookingRelease a held or confirmed slot of this session, so the slot is free again.
Inferred read-onlyget_bookingRead the state of a session: the understood intent and its open question, the bids of the current round and every hold with its present status and link.
Inferred read-onlyregister_agentGet this agent its own identity, once: answers an `agent` id and a `key`.
Inferred read-onlylink_phoneTie this agent to the phone number of the person it books for: the hub texts that number a six-digit code naming this agent, and `confirm_phone` spends it.
Inferred read-onlyconfirm_phoneSpend the code that link_phone texted, and tie this agent to that number.
Inferred read-onlycapabilitiesWhat this hub can do, in one call: every tool by name, every resource by URI, every prompt by name, the per-client budgets, how to authenticate, the protocol revision and where the documentation is.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.intent-hub]
url = "https://openintentprotocol.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"intent-hub": {
"type": "http",
"url": "https://openintentprotocol.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: intent-hub
Remote MCP URL: https://openintentprotocol.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"intent-hub": {
"url": "https://openintentprotocol.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"intent-hub": {
"type": "http",
"url": "https://openintentprotocol.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "intent-hub",
"transport": "streamable-http",
"url": "https://openintentprotocol.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.