Configuration

Preview

The MCP integration is in preview - tools, parameters, and behavior may change between releases.

Every MCP client needs three pieces of information: the endpoint URL, the transport to use, and the authentication header. This page covers all three.

Endpoints

The MCP server is mounted at /mcp on the same hosts as the Dime.Scheduler public API.

Environment	URL	Status
Sandbox	https://sandbox.api.dimescheduler.com/mcp	Available (preview)
Production	Not yet available	Planned

Pick sandbox for experiments

Use the sandbox environment for first contact and for any client that an end-user will configure themselves. It carries no production planning data.

Transport

The Dime.Scheduler MCP server speaks the Streamable HTTP transport defined by the MCP specification. This is the default in every modern MCP client. There is no stdio binary to install - the server is reached over plain HTTPS.

If your client only supports stdio (some older versions of Claude Desktop, for example), use the mcp-remote bridge:

{
  "mcpServers": {
    "dimescheduler": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://sandbox.api.dimescheduler.com/mcp",
        "--header",
        "X-API-KEY:${DIME_API_KEY}"
      ]
    }
  }
}

See Clients for full examples per product.

Authentication

Authentication is a single custom header on every request:

Header	Value
X-API-KEY	A valid Dime.Scheduler API key

The server rejects requests without a valid key with HTTP 401 Unauthorized. Keys carry the same scope as the user that created them, so the MCP client can only see and modify data that user is allowed to see.

Treat the API key like a password

The key gives full programmatic access to the tenant it was created in. Don't paste it into chat windows, screenshots, or shared configuration files. Use your client's encrypted secret store wherever possible.

Tool discovery

Once connected, the client should call the standard MCP tools/list method to discover the available tools and their JSON schemas. There is no separate manifest URL - the server returns the full tool catalog over the live MCP session.

You can inspect the catalog interactively with the MCP Inspector before wiring it up to a real assistant.

Time zones

Many tools take a timeZone parameter as an IANA identifier (Europe/Brussels, America/New_York, …). Always pass the time zone of the end user, not the server - the assistant should infer it from context or ask if it isn't sure. The parse_relative_time tool exists specifically to convert phrases like "next week" into concrete UTC ranges.