mcpbeat Sign in

Nookal MCP by usefulapi MCP Server

answering

Nookal MCP by usefulapi is answering right now. Last checked 7 min ago. It exposes 11 tools. Last commit 10 Oct 2026.

Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices.

Uptime history 70 hours of history
70 hours agonow
100.0%
Uptime 24h
92 of 92 checks
11
Tools
read from the server
101 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
and 3 more, back to 9 October 2026

Nothing serious here today

Today is the operative word: we check Nookal MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add nookal --transport http https://nookal.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "nookal": {
      "url": "https://nookal.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.nookal]
url = "https://nookal.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nookal": {
      "url": "https://nookal.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "nookal": {
      "url": "https://nookal.usefulapi.io/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nookal
nookal_get_availability
Get the free appointment slots per date between two dates (max 60 days, Nookal's limit), optionally for given locations, practitioners and a service. Each slot has its date, start time (24h, clinic local time), provider id and location id. Read-only: it does not book anything. Nookal GraphQL: availabilities.
nookal_get_client
Get one client (patient) by id: name, date of birth, contact details, addresses, alerts, allergies, notes, occupation, referring doctor and their treatment cases; optionally a summary of their invoices (totals and balances). Health-fund, pension and online-booking codes are not returned. Nookal GraphQL: clients.
nookal_list_appointments
List appointments (date, start/end time, status, type, client, practitioner, case, location, arrived / did-not-arrive flags, notes), filtered by date range, location, client, practitioner, type and status. Dates are clinic local. Nookal GraphQL: appointments.
nookal_list_cases
List treatment cases (id, client, title, start and referral dates, referrer, primary practitioner, notes), filtered by client, case or practitioner. Nookal GraphQL: cases.
nookal_list_classes
List the class types offered (id, name, category, duration, price, location, online-booking settings) — the class definitions, not individual sessions. Nookal GraphQL: classes.
nookal_list_invoices
List invoices with their line items and payments (number, client, case, location, practitioner, date, subtotal, tax, total, paid, balance), filtered by location, invoice id or creation date. For one client's invoices use get_client with include_invoices. Nookal GraphQL: invoices.
nookal_list_locations
List the clinic's locations (id, name, address, time zone, active). Location ids are needed by most other tools. Only the locations your API client was granted are returned. Nookal GraphQL: locations.
nookal_list_payments
List payments received against invoices (method, amount, date, reference, invoice, client, location), filtered by invoice or payment date. Nookal GraphQL: payments.
nookal_list_services
List the appointment types / services offered (id, name, category, duration in minutes, price, location, online-booking settings). Use a service id in get_availability. Nookal GraphQL: services.
nookal_list_staff
List staff members and practitioners (id, name, title, speciality, email, location ids, whether they are a provider / bookable online / active). Use the staff ids as provider_ids in list_appointments and staff_ids in get_availability. Nookal GraphQL: staff.
nookal_search_clients
Find clients (patients) by name, date of birth, mobile, email or id. Returns id, name, date of birth, location, active/deceased flags and contact details. With partial_match, names match on their first letters (e.g. 'Sm' finds Smith). Nookal GraphQL: clients.

Endpoints

URLTransportStateLatencyChecked
https://nookal.usefulapi.io/mcp streamable-http answering 99 ms 7 min ago

Alternatives to Nookal MCP by usefulapi

same job, measured the same way
Cliniko MCP by usefulapi
by usefulapi

Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.

17 tools answering
IntakeQ MCP by usefulapi
by usefulapi

Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits.

19 tools answering
Bookeo MCP by usefulapi
by usefulapi

Check Bookeo availability and manage bookings, holds and customers; read payments.

21 tools answering
Current RMS MCP by usefulapi
by usefulapi

Browse opportunities, products, stock, availability and invoices, and create quotes in Current RMS.

20 tools answering
Teachworks MCP by usefulapi
by usefulapi

Read Teachworks students, families, tutors, lessons, invoices and payments; book lessons.

24 tools answering
Harvest MCP by usefulapi
by usefulapi

Read time entries, projects, clients, tasks and invoices; log and update tracked time.

20 tools answering
Wild Apricot MCP by usefulapi
by usefulapi

Look up members, events, registrations, invoices and payments, and add contacts or check in guests.

21 tools answering
Lago MCP by usefulapi
by usefulapi

Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events.

24 tools answering

Nookal MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Nookal MCP by usefulapi do?
It exposes 11 tools, read directly from the server on our last check. Among them: nookal_get_availability, nookal_get_client, nookal_list_appointments, nookal_list_cases, nookal_list_classes, nookal_list_invoices and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Nookal MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 101 ms. The bar chart above shows every period we have measured.
How do I connect Nookal MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Nookal MCP by usefulapi need an API key?
No. Nookal MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Nookal MCP by usefulapi?
It answers our handshake in 101 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Nookal MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.