Doctolib MCP Server for Claude Desktop 8 tools — connect in under 2 minutes
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Doctolib and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"doctolib": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Doctolib MCP Server
Connect your Doctolib partner account to any AI agent and take full control of your healthcare scheduling and practitioner research through natural conversation.
Claude Desktop is the definitive way to connect Doctolib to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
What you can do
- Practitioner Discovery — Search for doctors and specialists by specialty and city, identifying bounded office locations and member approximations natively
- Availability Tracking — Identify bounded routing spaces verifying absolute time availability slots attached directly matching the targeted doctor
- Appointment Management — List complex mappings evaluating exactly scheduled times and identifying physical reservations active within your account
- Live Booking — Commands the backend orchestrating real-time database locks inserting explicit reservation parameters structurally binding to an exact time slot
- Visit Motive Identification — Read available reason categories explicitly supported by a given Practitioner required for slot lock verification
- Practice Navigation — Perform structural extraction of localized entity bounds configuring the raw office locations active within the application
- Specialty Mapping — Enumerate explicitly attached structured roles defining valid medical specialties and practitioner targets globally
The Doctolib MCP Server exposes 8 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Doctolib to Claude Desktop via MCP
Follow these steps to integrate the Doctolib MCP Server with Claude Desktop.
Open Claude Desktop Settings
Go to Settings → Developer → Edit Config to open claude_desktop_config.json
Add the MCP Server
Paste the configuration above into the mcpServers section
Restart Claude Desktop
Close and reopen Claude Desktop to load the new server
Start using Doctolib
Look for the 🔌 icon in the chat. your 8 tools are now available
Why Use Claude Desktop with the Doctolib MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with Doctolib through the Model Context Protocol.
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Doctolib + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the Doctolib MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Doctolib MCP Tools for Claude Desktop (8)
These 8 tools become available when you connect Doctolib to Claude Desktop via MCP:
consulter_praticien
Consulter le profil d'un praticien
disponibilites
Vérifier les créneaux disponibles pour un praticien
lister_cabinets
Lister les cabinets médicaux
lister_rendez_vous
Lister les rendez-vous pris
lister_specialites
Lister toutes les spécialités médicales disponibles
motifs_consultation
Lister les motifs de consultation d'un praticien
prendre_rendez_vous
Prendre un rendez-vous médical
rechercher_praticiens
Restricts search to explicit city boundaries natively bypassing local lists. Rechercher des praticiens par spécialité et ville
Example Prompts for Doctolib in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with Doctolib immediately.
"Search for general practitioners in Paris"
"What are the available slots for Dr. Martin (ID: 123) tomorrow?"
"List my upcoming medical appointments"
Troubleshooting Doctolib MCP Server with Claude Desktop
Common issues when connecting Doctolib to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
Doctolib + Claude Desktop FAQ
Common questions about integrating Doctolib MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.Is there a limit on the number of tools per server?
Does Claude Desktop support Streamable HTTP transport?
Connect Doctolib with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Doctolib to Claude Desktop
Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.