Claude Desktop Chronary Prompt/find_meeting_time

How to: Claude Desktop Chronary find_meeting_time

client:Claude Desktop transport:streamable-http prompt:find_meeting_time

Add Chronary to Claude Desktop

01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.chronary.ai/mcp"
      ]
    }
  }
}

02
Save the file and restart Claude Desktop.
03
find_meeting_time is surfaced in the attachment menu, under the server's name. Unlike a tool, you invoke it deliberately — Claude Desktop will not call it for you.
04
If it does not appear, check that Chronary is connected and that you are looking at its prompts rather than its tools.

Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs

Set these first

Chronary will not start until these are set, so it never reaches Claude Desktop.

CHRONARY_API_KEY

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.

Chronary MCP server