Model Context Protocol (MCP) Support

Status: Closed Testing

This feature is currently in closed testing phase. Contact us if you're interested in participating.

Integration with the Model Context Protocol (MCP), making Dime.Scheduler features accessible via this emerging protocol. This enables new ways to interact with Dime.Scheduler capabilities.

MCP Server Endpoint

The MCP server is available at:

Sandbox: https://sandbox.api.dimescheduler.com/mcp

Supported Tools

The MCP integration provides the following tools. All tools accept one optional parameter: jobNo.

get_open_tasks

Gets the unplanned (open) tasks that must yet be planned by the dispatcher.

Parameters:

• jobNo (optional): Job number to filter tasks

Sample prompt:

"What are the open tasks for project PROJECT001?"

get_recommendations

Gets recommended resources with available time slots for a given date range with optional skill filters and location-based scoring. The requirements parameter accepts natural language (e.g., 'plumber', 'electrician', 'plumbing skills') and will automatically match to the correct filter values in the system.

Parameters:

• jobNo (optional): Job number to filter recommendations
• startDate (required): The start date and time for the availability search window (ISO 8601 format, e.g., 2024-01-01T00:00:00Z)
• endDate (required): The end date and time for the availability search window (ISO 8601 format, e.g., 2024-01-31T23:59:59Z)
• requirements (optional): List of skills, requirements, or qualifications in natural language (e.g., 'plumber', 'electrician', 'plumbing', 'HVAC'). Can be comma-separated. The system will automatically match these to the correct filter values.
• duration (optional): Required duration for the task in ISO 8601 format (e.g., PT2H for 2 hours, PT30M for 30 minutes)
• locationAddress (optional): Location address string for proximity-based resource scoring
• locationCountry (optional): Country code for geocoding (e.g., US, CA, GB)
• locationLatitude (optional): Latitude for location (if address not provided)
• locationLongitude (optional): Longitude for location (if address not provided)
• granularity (optional): Time slot granularity in ISO 8601 format (e.g., PT15M, PT30M)
• locationMode (optional): Location mode: 'home' (default) or 'actual' (current GPS location)
• maxResults (optional): Maximum number of results to return
• maxDistanceKm (optional): Maximum distance in kilometers for resource filtering
• timeZone (optional): IANA timezone identifier (e.g., Europe/Brussels, America/New_York)

Sample prompt:

"Who is available this week for a 2-hour job nearby London (UK) with the skill electrician?"

get_resource_planning

Fetches the planning (appointments) for one or more resources by their display names during a specified time range.

Parameters:

• jobNo (optional): Job number to filter planning
• resourceDisplayNames (required): The display names of the resources to fetch planning for (comma-separated)
• startDateTime (required): The start date and time for the planning period (ISO 8601 format, e.g., 2024-01-01T00:00:00Z)
• endDateTime (required): The end date and time for the planning period (ISO 8601 format, e.g., 2024-01-31T23:59:59Z)

Sample prompt:

"Give me the planning for resource Johnny Marr for this week."

Open Source Playground

We have an open source playground that you can use to explore some of the capabilities of our MCP server. The playground provides a hands-on way to test and interact with the MCP integration.

GitHub Repository: dime-scheduler/mcp-examples