Mcp日程表server

Created By
Damon-lawa year ago
配套MCP日程表(VSCode插件拓展) 使用的一个MCP Server, 实现日程的自然语言描述增,查,删。
Overview

What is MCP日程表 Server?

MCP日程表 Server is a backend server designed to work with the MCP日程表 VSCode plugin, enabling users to manage their schedules through natural language commands.

How to use MCP日程表 Server?

To use the MCP日程表 Server, install the MCP日程表 plugin from the Visual Studio Marketplace, clone the project, install dependencies, and run the server. You can then interact with the server using natural language commands in your IDE.

Key features of MCP日程表 Server?

  • Natural language processing for schedule management (add, delete, query)
  • Integration with popular IDEs like VSCode and Trae
  • Real-time reminders and notifications for scheduled events

Use cases of MCP日程表 Server?

  1. Adding reminders for important tasks or events.
  2. Querying current schedules and upcoming events.
  3. Deleting or modifying existing schedules through simple commands.

FAQ from MCP日程表 Server?

  • Can I use MCP日程表 Server with any IDE?

Currently, it is designed for use with VSCode and Trae.

  • Is there a mobile version of the MCP日程表?

No, it is primarily a server for desktop IDEs.

  • How do I configure the server?

You need to set the server command in your IDE configuration to point to the MCP日程表 Server.

Server Config

{
  "mcpServers": {
    "schedules": {
      "command": "node 你的路径\\mcp_server_for_schedules\\build\\index.js --port 3001"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Damon-law
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

33 minutes ago