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)에서만 되고 웹이나 모바일은 안 돼요
Calendar Ics Events Free Busy을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ 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는 웹에서 도는 서버만 연결할 수 있어요
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 스타i세 기둥: 리뷰 · 점검 · 사용 정도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: