Model Context Protocol (MCP)

Status: Preview

The MCP integration is currently in preview. Tool names, parameters, and behavior may change between releases. It is not recommended for production workloads yet.

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external systems through a uniform JSON-RPC interface. The Dime.Scheduler MCP server exposes the most common scheduling operations - listing tasks, finding available resources, creating and rescheduling appointments - as MCP tools that any compliant client can call.

What you can do with it

With an MCP-capable assistant connected to Dime.Scheduler, you can:

• Ask in plain language - "Who is available next Tuesday afternoon for a 2-hour electrical job in Antwerp?"
• Schedule and reschedule appointments - create, move, reassign, or cancel work orders directly from chat.
• Inspect the planning - pull a resource's calendar for the week, search appointments, or look up open tasks.
• Discover the right resource - match jobs to skills, location, and availability through the recommendation tool.
• Drive automations - embed Dime.Scheduler tools in larger AI workflows alongside calendars, CRMs, and ticketing systems.

How it fits in the integration landscape

Connector	Audience	Style
Business Central / NAV	Back-office sync	Bidirectional, transactional
Exchange	Calendar sync	Bidirectional, scheduled
Webhooks	Custom downstream systems	Outbound, event-driven
Zapier / Logic Apps	No-code automation	Bidirectional, workflow
MCP	AI assistants and agents	On-demand, conversational

MCP complements the existing connectors: it does not replace your back-office sync, but it unlocks a new conversational entry point on top of the same data.

Architecture

AI assistant (Claude, Cursor, …)  ──►  MCP client
                                              │  JSON-RPC over Streamable HTTP
                                              ▼
                            https://<env>.api.dimescheduler.com/mcp
                                              │
                                              ▼
                                  Dime.Scheduler API

Every request is authenticated with the same API keys you already use for the public API. The MCP server is stateless - it translates tool calls into Dime.Scheduler API calls and streams the results back to the assistant.

Supported tool categories

The server exposes tools across the following areas. Each is documented on its own page:

• Tasks & Jobs - list open tasks, search tasks and jobs.
• Resources - list resources, inspect skills and capacity, find available slots, get recommendations.
• Appointments - search, inspect, create, update, reschedule, and delete appointments.
• Reference data & utilities - categories, time markers, relative-time parsing.

Next steps

1. Check the Prerequisites.
2. Pick the right endpoint and authentication for your environment.
3. Connect your favorite MCP client - Claude Desktop, Cursor, the MCP Inspector, or your own.
4. Try the example prompts to get a feel for what's possible.