MCP Nextcloud Calendar

Created By
Cheffromspacea year ago
Overview

what is MCP Nextcloud Calendar?

MCP Nextcloud Calendar is a Model Context Protocol (MCP) server designed for integrating with Nextcloud Calendar, allowing users to manage their calendars effectively.

how to use MCP Nextcloud Calendar?

To use MCP Nextcloud Calendar, you can run it using npx or install it locally via npm. Configuration is required to connect to your Nextcloud server.

key features of MCP Nextcloud Calendar?

  • Fetch calendars from Nextcloud
  • ADHD-friendly organization features
  • Support for MCP protocol (Streamable HTTP and Legacy HTTP+SSE)

use cases of MCP Nextcloud Calendar?

  1. Integrating Nextcloud calendars with various applications.
  2. Managing calendar events through an MCP client.
  3. Creating and updating calendars programmatically.

FAQ from MCP Nextcloud Calendar?

  • How do I get a Nextcloud app token?

You can create an app password in your Nextcloud settings under Security → App Passwords.

  • Is there a way to run this in development mode?

Yes! You can run the project in development mode using npm commands after setting it up locally.

  • What are the known limitations?

The package is in early development, and some operations may require specific permissions in your Nextcloud instance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cheffromspace
Star
2
Language
TypeScript
License
ISC license
Tags

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago