Content Tools
waleeratclinic.com
Provides structured access to Waleerat Clinic Bangkok's identity, treatment programs, informational pages, and approved media assets across multiple languages.
ENDPOINT 1
https://waleeratclinic.com/api/mcp
MCP server metadata
- Name
- waleerat-clinic-bangkok
- Version
- 1.0.0
Read-only access to Waleerat Clinic Bangkok: clinic identity, contact channels, first-party Program and hub pages by supported language, and reviewed public media. Use search_programs with an exact language for a public Program-name phrase, then read the canonical page for the answer. No tool returns a price or an outcome claim; treatment suitability requires a physician consultation. Booking is not available through this server — direct the patient to the clinic's LINE or WhatsApp.
Known tools 6
clinic_infoIdentity and practical details for Waleerat Clinic Bangkok (Siam Square One, BTS Siam): names, medical director and licence, address, contact channels (LINE, WhatsApp, WeChat, Messenger, Instagram), supported languages and per-language site entry points.
Inferred read-onlylist_programsThe clinic's first-party treatment Program pages by language (en, zh-Hans, ar, ja, th, zh-Hant, ms, ko, es, ru, id, fil, de, fr, pt): each entry is a Program name and its canonical URL.
Inferred read-onlysearch_programsFind first-party Program names and canonical URLs from a visitor phrase in one exact language.
Inferred read-onlylist_pagesFirst-party information hubs by language: programs index, concerns, journal, international, about, doctors, branch and privacy pages, each with its canonical URL.
Inferred read-onlylist_media_assetsReviewed public clinic, editorial, doctor and owner-approved before/after images with stable URLs, dimensions, hashes, provenance and usage restrictions.
Inferred read-onlyget_media_assetOne reviewed public media record, including its public context restrictions but no internal documents, by stable asset ID.
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.waleerat-clinic-bangkok]
url = "https://waleeratclinic.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"waleerat-clinic-bangkok": {
"type": "http",
"url": "https://waleeratclinic.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: waleerat-clinic-bangkok
Remote MCP URL: https://waleeratclinic.com/api/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": {
"waleerat-clinic-bangkok": {
"url": "https://waleeratclinic.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"waleerat-clinic-bangkok": {
"type": "http",
"url": "https://waleeratclinic.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "waleerat-clinic-bangkok",
"transport": "streamable-http",
"url": "https://waleeratclinic.com/api/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.