eCommerce
kadro.co
An MCP server for Kadro that enables searching photography/videography shoot types and photographers, viewing bookable packages and prices, creating reservations, and obtaining payment links.
ENDPOINT 1
https://www.kadro.co/mcp
MCP server metadata
- Name
- kadro-booking
- Version
- 1.0.0
Known tools 6
search_photographersFind real, bookable photographers for a given shoot_type_id (from search_shoot_types), optionally narrowed to a city_id.
Inferred read-onlyget_photographer_packagesList the real, currently bookable packages (with prices, in Toman) a specific photographer offers for a given shoot_type_id.
Inferred read-onlycreate_reservationBook a specific photographer for a specific package, date/time, and address on the user's behalf — no login required.
Inferred read-onlyget_payment_linkGet a URL for the human to open in their own browser to finish this reservation: verify their phone number by SMS code and pay.
Potential side effectsCONNECT 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.kadro-booking]
url = "https://www.kadro.co/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"kadro-booking": {
"type": "http",
"url": "https://www.kadro.co/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: kadro-booking
Remote MCP URL: https://www.kadro.co/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": {
"kadro-booking": {
"url": "https://www.kadro.co/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"kadro-booking": {
"type": "http",
"url": "https://www.kadro.co/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "kadro-booking",
"transport": "streamable-http",
"url": "https://www.kadro.co/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.