Chronary MCP server

official from Chronary Active last commit 2 mo

{
  "mcpServers": {
    "chronary": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp@latest",
        "npx"
      ],
      "env": {
        "CHRONARY_API_KEY": "<chronary_api_key>"
      }
    }
  }
}

{
  "mcpServers": {
    "chronary": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp@latest",
        "npx"
      ],
      "env": {
        "CHRONARY_API_KEY": "<chronary_api_key>"
      }
    }
  }
}

{
  "mcpServers": {
    "chronary": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp@latest",
        "npx"
      ],
      "env": {
        "CHRONARY_API_KEY": "<chronary_api_key>"
      }
    }
  }
}

{
  "servers": {
    "chronary": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp@latest",
        "npx"
      ],
      "env": {
        "CHRONARY_API_KEY": "${input:chronary_api_key}"
      }
    }
  },
  "inputs": [
    {
      "id": "chronary_api_key",
      "type": "promptString",
      "description": "Chronary api key",
      "password": true
    }
  ]
}

{
  "mcpServers": {
    "chronary": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp@latest",
        "npx"
      ],
      "env": {
        "CHRONARY_API_KEY": "<chronary_api_key>"
      }
    }
  }
}

file .mcp.json (in your project root)install npx -y @chronary/mcpversion 1.5.2

Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.