Chronary

Name: Chronary
Author: Chronary

by Chronaryversion 1.5.2i★ –iComputer or cloud

Registry nameai.chronary/mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Docs, sheets & office work
You need to fill in: CHRONARY_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: CHRONARY_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Or run it on your computer

claude mcp add chronary --env CHRONARY_API_KEY=your-value -- npx -y @chronary/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chronary": {
      "type": "http",
      "url": "https://api.chronary.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chronary": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@chronary/mcp"
      ],
      "env": {
        "CHRONARY_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CHRONARY_API_KEY secret required env
Chronary API key - org key (chr_sk_...) or agent-scoped key (chr_ak_...). Request access at https://chronary.ai.
Authorization secret required HTTP header
Bearer auth with your Chronary API key, e.g. 'Bearer chr_sk_...'.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain chronary.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2191 servers in this category
Published to the registry more recently than 18% of the other 2191 servers in this category
Basic checks equal to or better than 100% of the other 2191 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Chronary safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CHRONARY_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.5.2) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@chronary/mcp

MCP server for Chronary — calendar tools for AI assistants.

Drops 50 calendar tools (manage agents, calendars, and events, request human Google/Microsoft setup, find meeting times, run scheduling proposals, configure availability rules, manage webhooks, iCal subscriptions, scoped keys, audit log, and usage) into any MCP-compatible client: Claude Desktop, Cursor, VS Code Copilot, Claude Code, Windsurf.

One-click install via [Smithery](https://smithery.ai/server/chronary/agent-calendar): npx -y @smithery/cli mcp add chronary/agent-calendar --client claude (swap --client for cursor, vscode, claude-code, windsurf, …).

Prerequisites

A Chronary account — sign up at chronary.ai.
An API key from the console (starts with chr_sk_).
Node.js ≥ 18 on the machine where the MCP client runs.

Client configurations

All examples use npx -y @chronary/mcp, which downloads and runs the latest version on demand. No install step required.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

macOS / Linux:

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

Windows (uses cmd /c because spawn can't resolve npx.cmd directly):

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

Restart Claude Desktop after saving.

Cursor

Edit .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (user-level):

macOS / Linux:

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

Windows:

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

VS Code Copilot

Edit .vscode/mcp.json (workspace) or run the MCP: Open User Configuration command for a user-level config. VS Code uses a different top-level key (servers) and requires an explicit type:

macOS / Linux:

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

Windows:

"servers": { "chronary": { "type": "stdio", "command": "cmd", "args": ["/c", "npx", "-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }

Claude Code

Edit .mcp.json at the project root, or ~/.claude.json for user-level:

macOS / Linux:

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

Windows:

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

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json (%USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows):

macOS / Linux:

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

Windows:

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

Windsurf limit: Cascade enforces a hard cap of 100 total tools across all MCP servers and 20 tool calls per prompt. Chronary exposes 50; consider --tools filtering if you stack multiple servers.

Reducing context with `--tools`

Exposing all 50 tools uses LLM tokens on every request. For focused workflows, whitelist only what you need:

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

Pointing at a non-production API

For self-hosted Chronary instances or development against a local API:

"args": ["-y", "@chronary/mcp", "--base-url", "http://localhost:8787"] }

Tools exposed

Tool	Read-only	Destructive
`list_calendars`, `get_calendar`	✓
`create_calendar`, `update_calendar`
`delete_calendar`		✓
`list_events`, `get_event`	✓
`create_event`, `update_event`, `confirm_event`
`cancel_event`, `release_event`		✓
`list_agents`, `get_agent`	✓
`create_agent`, `update_agent`
`delete_agent`		✓
`get_availability`, `find_meeting_time`	✓
`get_calendar_context`	✓
`list_proposals`, `get_proposal`	✓
`create_proposal`, `respond_to_proposal`, `resolve_proposal`
`cancel_proposal`		✓
`get_availability_rules`	✓
`set_availability_rules`
`clear_availability_rules`		✓
`list_webhooks`, `get_webhook`, `list_webhook_deliveries`	✓
`create_webhook`, `update_webhook`
`delete_webhook`		✓
`list_ical_subscriptions`, `get_ical_subscription`	✓
`subscribe_ical`, `update_ical_subscription`, `sync_ical_subscription`
`delete_ical_subscription`		✓
`list_scoped_keys`	✓
`create_scoped_key`
`revoke_scoped_key`		✓
`get_audit_log`	✓
`accept_terms`
`get_usage`	✓

Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are surfaced to MCP clients so hosts can decide whether to require user confirmation.

Troubleshooting

"spawn npx ENOENT" on Windows — use the cmd /c npx ... form shown above.

"CHRONARY_API_KEY is required" — the env block must be nested under the server entry, not at the top of the config file.

Tools aren't showing up — restart the MCP client after editing the config. Most clients only read the config on startup.

Verify the binary runs locally:

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

License

Apache-2.0

Chronary

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

@chronary/mcp

Prerequisites

Client configurations

Claude Desktop

Cursor

VS Code Copilot

Claude Code

Windsurf

Reducing context with --tools

Pointing at a non-production API

Tools exposed

Troubleshooting

Links

License

Reducing context with `--tools`