MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Read an .ics export: list events with recurring series expanded, find free and busy, bill a meeting.
作者による原文
この種の作業を AI に教える Skill。これと一緒に使えます
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 0/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 12/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 0/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 12/100 |
品質: 基本チェック 2/3 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
チェック 2/3 合格 · あなたのパソコンで動きます
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげますが、先に準備が必要です
キー不要、インストール不要 · パソコン版 Claude アプリ(Windows または Mac)のみ。Web やスマホでは使えません
Calendar Ics Events Free Busy を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Calendar Ics Events Free Busy を使っていると言うか、回答に Calendar Ics Events Free Busy のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT はまだ Calendar Ics Events Free Busy につなげません
Calendar Ics Events Free Busy はパソコンに入れて使うものですが、ChatGPT は Web 上で動くサーバーにしかつなげません
Claude Code はまだ Calendar Ics Events Free Busy につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · Calendar Ics Events Free Busy につなげるアプリを使う
Cursor はまだ Calendar Ics Events Free Busy につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · Calendar Ics Events Free Busy につなげるアプリを使う
VS Code はまだ Calendar Ics Events Free Busy につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · Calendar Ics Events Free Busy につなげるアプリを使う
MCP_LICENSE_KEY 秘密 env説明は自動翻訳です。変数名は原文のままです。迷ったら原文を確認してください。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
mcpb: …/calendar.mcpbこのサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
パソコン上で動かせるアプリ
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月20日にチェック
公開者(bestremotetools.com)がリポジトリの所有者(theluckystrike)ではありません。別の人が登録した可能性があります
コードの最終更新:一昨日
MITを使用
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/bestremotetools-calendar-ics-events-free-busy)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち2項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は一昨日、最新バージョン(0.21.0)がレジストリに届いたのは2 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにMCPBも必要です。
同じカテゴリには:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| これ Calendar Ics Events Free Busy | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 動く場所 | パソコンにインストールが必要 | クラウドで動き、インストール不要 | パソコンにインストールが必要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | パソコンにインストールが必要 |
| キーが必要 | いいえ | いいえ | いいえ | はい | いいえ | いいえ |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | はい | いいえ |
| 基本チェック | 2/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| ライセンス | MIT | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Your calendar app can show you next Tuesday. It cannot tell you where your week actually went, which two things you said yes to at the same time, or how many billable hours last month's meetings were worth. This server reads the .ics file your calendar already exports and answers those questions: events in any window with recurring series expanded properly, merged busy blocks and the real free gaps inside your working hours, every double booking across work and personal calendars at once, a clean .ics of just the events you picked, and the exact time entry for a meeting you should have billed. No account is connected, nothing is synced, and the calendar file stays on your machine as plain text.
Built by theluckystrike.
In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fcalendar-ics-reader-events-freebusy-conflicts/versions/latest) (io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts).
Listed on the [AI Product Index](https://index.percall.dev/l/zovo-calendar.html) - live remote endpoint at mcp.zovo.one/s/calendar, free tier, no signup.
Import the .ics your calendar exports, then ask what is on, when you are free, and what clashes, zero setup, all local.
npm publish for @theluckystrike/mcp-calendar is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.
One-click (.mcpb): download calendar.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest
(claude_desktop_config.json):
{
"mcpServers": { "calendar": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-calendar"] } } }
Claude Code:
claude mcp add calendar -- npx -y @theluckystrike/mcp-calendar
(.cursor/mcp.json):
{
"mcpServers": { "calendar": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-calendar"] } } }
The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these four commands:
git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers
npm install npm run build -w packages/mcp-license -w servers/timezone -w servers/calendar
Then point your client's command at node with one arg: the absolute path to servers/calendar/dist/index.js.
To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.
| App | Where |
|---|---|
| Google Calendar | Settings -> Import & export -> Export. You get a zip; import the .ics inside it. |
| Apple Calendar | File -> Export -> Export... |
| Outlook (desktop) | File -> Save Calendar, format iCalendar (.ics) |
| Outlook / Microsoft 365 (web) | Settings -> Calendar -> Shared calendars -> Publish, then use the ICS link (Pro) |
| Anything else | Any published feed URL ending in .ics, or webcal:// (Pro) |
Then: ics_import {path: "~/Downloads/mike@example.com.ics", name: "work"}
| Tool | What it does |
|---|---|
ics_import | Read a .ics file (path), pasted contents (text) or a public feed (url, Pro) and keep it locally under a name. Importing the same name again replaces it. |
calendars_list | Every imported calendar: name, source, event count, size, when it was imported. |
events_list | Every event between two dates with recurring series expanded to real occurrences, sorted, in your own time zone. Each row carries an id. |
events_search | Events whose title, description, location, organizer or attendees contain a phrase. |
free_busy | Merged busy blocks and the free gaps inside your working hours, day by day. Events marked free/transparent do not count as busy. |
conflicts | Every pair of events that overlap, with the overlap in minutes -- across all calendars, so a client call clashing with a school run is caught. A longer window is shortened to the free 31 days and answered, never refused. |
next_event | The next thing that has not started, and how long until it does. |
event_export | Write chosen events (by id, or a whole window) to a new .ics you can send. Times in UTC, so it lands correctly in any client. |
event_to_time_entry | Turn one meeting into the exact arguments for the time-tracker's entry_add, so a call becomes billable time without retyping it. |
ics_forget | Remove one calendar and its local copy. |
license_status / license_activate | Show the tier; activate a Pro key offline. |
Resource calendar://today gives today's schedule in one read. Prompt plan_my_day walks the whole loop: what is on, what clashes, where the free stretches are, and which finished meetings to bill.
Written against real exports, not just the spec: line folding (CRLF, bare LF and bare CR, and folds that Exchange places inside a multi-byte character, which are rejoined on the bytes before decoding), \n \, \; \\ escaping, whole-day events with an exclusive DTEND, DURATION instead of DTEND, TZID and UTC times, floating times, RRULE for HOURLY, DAILY, WEEKLY, MONTHLY and YEARLY with COUNT, UNTIL (inclusive), INTERVAL, BYDAY including ordinals (2MO, -1FR), BYMONTHDAY, BYMONTH and BYSETPOS, EXDATE, RDATE, RECURRENCE-ID overrides (the moved instance replaces the original instead of appearing twice), STATUS:CANCELLED, TRANSP:TRANSPARENT, and VALARM blocks inside an event. An event it cannot read is skipped and counted rather than costing you the rest of the file.
FREQ=MINUTELY and FREQ=SECONDLY are deliberately not expanded: one such rule fills any window with thousands of occurrences and buries the rest of the week. Those events are listed at their first occurrence and the reason is said out loud. A rule with no COUNT and no UNTIL is expanded only as far as the window you asked for.
Exports written by this server keep whole-day events as DATE values, so a holiday leaves as the same day it arrived rather than a timed block on the day before in your machine's zone.
VTIMEZONE is deliberately ignored. A file's inline DST rules are only as fresh as the app that wrote it; the TZID is kept and every offset is computed from the ICU data inside your Node build instead, which is what keeps a weekly Warsaw 10:00 meeting at 10:00 local across the March clock change.
| Free | Pro ($19 one-time) | |
|---|---|---|
| Calendars kept | 2 | unlimited |
| Window per question | up to 31 days | any window |
conflicts over a longer window | answered for the first 31 days, cap named | any window |
| Events per export | 50 | unlimited |
| Import from a URL or webcal feed | -- | yes |
| Everything else | full | full |
Get Pro, or $39 for every server in the suite, lifetime.
Everything is local. The calendar file you import is copied to ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/calendar/ and read from there; deleting that directory resets the server. There is exactly one network call in the whole server, and only when you pass a url yourself: it fetches that address once, with a 12-second timeout, a 5 MB cap, and a refusal on loopback, private and cloud-metadata addresses. Nothing is uploaded, no account is linked, and licence keys verify offline.
.ics engine from it: convert a meeting time, find slots across countries, write an invite.event_to_time_entry hands it a finished meeting; it tracks and reports the hours.No. There is no OAuth, no token and no sync. You export a file (or paste a public feed URL on Pro) and it is read locally. That also means an import is a snapshot: re-import when the calendar has moved on.
Yes, and that is most of the code. A weekly series is expanded on the wall clock, so a Warsaw 10:00 meeting stays 10:00 through the DST change rather than drifting to 11:00. Monthly on the 31st skips February instead of rolling into March, UNTIL includes the occurrence that falls exactly on it, and a single moved instance replaces the original.
It is not: RFC 5545 makes DTEND exclusive for a whole-day event, so 1--3 June means the 1st and the 2nd. This server follows the spec, which is what your calendar app does too.
It writes .ics files with event_export, which you can import anywhere. It never modifies the calendar it read.
5 MB, which is a few thousand events. Export a narrower date range if a full history is bigger than that.
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install: