Skip to main content

MCP

The Dime.Scheduler documentation is exposed as a Model Context Protocol (MCP) server, so AI agents can search and read it directly through tool calls instead of scraping HTML.

The endpoint is at:

https://docs.dimescheduler.com/api/mcp

It exposes two tools:

ToolPurpose
docs_searchFull-text search across all documentation pages. Returns titles, URLs and snippets ranked by relevance.
docs_fetchRetrieve the full markdown of a specific page by URL.

The server runs in stateless mode — every request is independent, no session is needed.

Add to Claude Code

claude mcp add --transport http dimescheduler-docs https://docs.dimescheduler.com/api/mcp

In any Claude Code session, ask Claude to search Dime.Scheduler docs and it will call the MCP tools automatically.

Add to Claude Desktop

In claude_desktop_config.json (%APPDATA%\Claude\ on Windows, ~/Library/Application Support/Claude/ on macOS):

{
"mcpServers": {
"dimescheduler-docs": {
"transport": {
"type": "http",
"url": "https://docs.dimescheduler.com/api/mcp"
}
}
}
}

Restart Claude Desktop to pick up the change.

Other MCP clients

The endpoint follows the Streamable HTTP transport of the MCP specification. Any MCP-compatible client can connect — point it at the URL above.

Test with curl

List the available tools:

curl -X POST https://docs.dimescheduler.com/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Run a search:

curl -X POST https://docs.dimescheduler.com/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"docs_search","arguments":{"query":"business central setup","limit":3}}}'

A GET request returns a status object — useful as a liveness check. The search index loads lazily on the first POST, so a fresh GET will report initialized: false until a real MCP call has been made against the same instance.