Enterprise DNAEnterprise DNA

MCP Servers

Chronary/chronary-mcp

MCP server for the Chronary calendar API

Visit site ↗

Our verdict

Not reviewed yet

We have not reviewed Chronary/chronary-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About Chronary/chronary-mcp

Chronary/chronary-mcp is an MCP server that exposes the Chronary calendar API through the Model Context Protocol. It allows AI agents to read and write calendar data using standard MCP tool calls. The server is written in TypeScript and follows the MCP specification.

Best for

Developers building MCP-based AI agents that need calendar integration with the Chronary service

Use cases

  • Integrating calendar event retrieval into AI assistants
  • Creating or updating events via natural language commands
  • Querying availability and scheduling through agent workflows

Notes

0 stars on GitHub. Last updated 2026-07-13. Licensed Apache-2.0.

Pros

  • Leverages the MCP standard for interoperability with MCP-compatible clients
  • Written in TypeScript for type safety and developer familiarity
  • Lightweight and focused on a single API surface

Cons

  • Zero stars on GitHub indicates a very new or unproven project
  • Dependent on the Chronary calendar API, which may have limited adoption or reliability
  • No community or documentation beyond the repository itself

Key facts

What we have checked

Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

CHRONARY_API_KEY=test npx -y @chronary/mcp --help

Tools exposed

  • delete_calendar
  • delete_agent
  • get_calendar_context
  • cancel_proposal
  • get_availability_rules
  • set_availability_rules
  • clear_availability_rules
  • delete_webhook
  • delete_ical_subscription
  • list_scoped_keys
  • create_scoped_key
  • revoke_scoped_key
  • get_audit_log
  • accept_terms
  • get_usage

Clients the listing names (not checked here)

Claude Desktop, Claude Code, Cursor, Windsurf, VS Code

Example client config

{
  "mcpServers": {
    "chronary": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp"
      ],
      "env": {
        "CHRONARY_API_KEY": "chr_sk_..."
      }
    }
  }
}

Install

Add Chronary/chronary-mcp to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (remote server)

claude mcp add --transport http chronary-chronary-mcp https://api.chronary.ai/mcp --header 'Authorization: Bearer YOUR_CHRONARY_CHRONARY_MCP_TOKEN'

Needs CHRONARY_CHRONARY_MCP_TOKEN: replace each YOUR_ value with your own.

Version 1.5.2 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Claude Desktop

Config checked

Add to claude_desktop_config.json (runs on your computer)

{
  "mcpServers": {
    "chronary-chronary-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp@1.5.2"
      ],
      "env": {
        "CHRONARY_API_KEY": "YOUR_CHRONARY_API_KEY"
      }
    }
  }
}

Needs CHRONARY_API_KEY: replace each YOUR_ value with your own.

Version 1.5.2 · From the Official MCP registry, read · Format checked against Claude Desktop's config docs

Cursor

Config checked

Add to .cursor/mcp.json (remote server)

{
  "mcpServers": {
    "chronary-chronary-mcp": {
      "url": "https://api.chronary.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CHRONARY_CHRONARY_MCP_TOKEN"
      }
    }
  }
}

Needs CHRONARY_CHRONARY_MCP_TOKEN: replace each YOUR_ value with your own.

Version 1.5.2 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (remote server)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "chronary-chronary-mcp-token",
      "description": "Bearer auth with your Chronary API key, e.g. 'Bearer chr_sk_...'.",
      "password": true
    }
  ],
  "servers": {
    "chronary-chronary-mcp": {
      "type": "http",
      "url": "https://api.chronary.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:chronary-chronary-mcp-token}"
      }
    }
  }
}

Needs CHRONARY_CHRONARY_MCP_TOKEN: replace each YOUR_ value with your own.

Version 1.5.2 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (remote server)

[mcp_servers.chronary-chronary-mcp]
url = "https://api.chronary.ai/mcp"
bearer_token_env_var = "CHRONARY_CHRONARY_MCP_TOKEN"

Needs CHRONARY_CHRONARY_MCP_TOKEN: replace each YOUR_ value with your own.

Version 1.5.2 · From the Official MCP registry, read · Format checked against Codex's config docs

  • ChatGPT: ChatGPT connects only to remote servers that need no API key.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What Chronary/chronary-mcp connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRemote server, version 1.5.2Config checkedClaude Code docs
Claude DesktopClientInstall recipe matches the client's documented formatRuns locally, version 1.5.2Config checkedClaude Desktop docs
CursorClientInstall recipe matches the client's documented formatRemote server, version 1.5.2Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRemote server, version 1.5.2Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRemote server, version 1.5.2Config checkedCodex docs

Sources

Where this comes from

No sources recorded yet. Each source we check is listed here with the date we checked it.

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →