Productivity
timeplex.ai
Searches for beauty and wellness shops, checks their services and availability, and facilitates booking appointments.
ENDPOINT 1
https://chat.timeplex.ai/mcp
MCP server metadata
- Name
- timeplex-booking
- Version
- 0.1.0
Known tools 6
get_shop_servicesGet a shop's service menu (name, price, duration) and its staff/seats.
Inferred read-onlyrequest_bookingSubmit a booking request for a shop that is not onboarded to Timeplex yet (bookable=false).
Inferred read-onlystart_bookingBuild a link that lets the customer continue the booking for the chosen shop, service and time.
Inferred read-onlyget_booking_statusLook up booking and payment status by reservation number, including whether it can be cancelled and the refund terms.
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.timeplex-booking]
url = "https://chat.timeplex.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"timeplex-booking": {
"type": "http",
"url": "https://chat.timeplex.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: timeplex-booking
Remote MCP URL: https://chat.timeplex.ai/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": {
"timeplex-booking": {
"url": "https://chat.timeplex.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"timeplex-booking": {
"type": "http",
"url": "https://chat.timeplex.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "timeplex-booking",
"transport": "streamable-http",
"url": "https://chat.timeplex.ai/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.