eCommerce
belcome.app
An MCP server for Belcome that enables users to find beauty and wellness businesses, list their services, and check available booking slots.
ENDPOINT 1
https://belcome.app/mcp
MCP server metadata
- Name
- Belcome
- Version
- 1.0.0
Book appointments at salons, barbershops, spas, med spas and studios that use Belcome. Flow: find_business, then list_services, then find_slots. Offer a few open times in the location's timezone and give the person the booking_url of the time they choose: they confirm it on the business's page with their name and phone. Never ask for health details, card numbers or passwords in the chat.
Known tools 3
find_businessFind salons, barbershops, spas and studios that take online bookings on Belcome, by name, service or city.
Inferred read-onlylist_servicesList the services a business offers online at one location: name, duration, price and the professionals who do each one.
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.belcome]
url = "https://belcome.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"belcome": {
"type": "http",
"url": "https://belcome.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: belcome
Remote MCP URL: https://belcome.app/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": {
"belcome": {
"url": "https://belcome.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"belcome": {
"type": "http",
"url": "https://belcome.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "belcome",
"transport": "streamable-http",
"url": "https://belcome.app/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.