MCP server URL:
https://developer.flabslis.com/mcpHow it works
The MCP exposes the same content you’re reading now — the auth token flow, CRM lead/booking endpoints, the billing pre-booking API, webhook events and the OpenAPI specs — as structured, searchable context. Your assistant pulls only the pages it needs, so it generates code against the current API instead of guessing.1. Add the MCP server to your editor
Pick your tool. The server is a remote HTTP MCP — no install, no API key needed to read the docs.- Cursor
- Claude Code
- VS Code (Copilot)
- Windsurf
Add to
.cursor/mcp.json in your project (or the global config):2. Ask the AI to integrate
Once the server is connected, describe what you want in plain language. The assistant will search the docs, read the relevant endpoints, and scaffold the code. A few prompts that work well:What the assistant can build
Authentication
Token generation and refresh handling with your client credentials.
CRM leads & bookings
Branch lookup, test/package pricing, and lead/booking creation.
Billing pre-bookings
Create pre-bookings that kick off the lab workflow.
Webhook handlers
Endpoints that react to bill, report and CRM events.
Tips for better results
- Tell it your account mode. Mention whether you’re catch-all (default) or party-scoped so it scopes calls correctly.
- Name your stack. “in Node/Express”, “in Python/FastAPI”, etc. produces idiomatic code.
- Ask it to verify against the docs. “Double-check the required fields against the flabs-developer MCP” catches missed parameters before you run anything.