OpenAgenda

Name: OpenAgenda
Author: openagenda

Search, analyze and manage events on OpenAgenda.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://openagenda--openagenda.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "OpenAgenda": {
      "url": "https://openagenda--openagenda.run.tools"
    }
  }
}

能力清单

工具

说明

search_docs

Find the OpenAgenda v3 operations relevant to a question. Returns operation signatures, parameters and examples to use from the `execute` tool.

execute

Run JavaScript against the OpenAgenda v3 API and return its result. A ready-to-use `oa` client (an OpenAgenda instance) is available. Every operation is `oa.<resource>.<action>({ path?, query? })`, is async, and resolves to { data, error } — it does NOT throw on HTTP errors, so check `error`. Call search_docs to discover the full catalogue with each operation's params, response shape and a runnable example, e.g.: oa.agendas.events.list({ path: { agendaUid }, query: { relative: ["upcoming"] } }) List endpoints return { data: [...], pagination: { after } } — pass query.after to page; facets returns { facets: {...} } (no data array, no pagination). A `schemas` namespace (zod validators, prefixed z…) is also available to validate payloads. Write an async body and `return` the value you want back (JSON-serialised). Compose freely: fetch, filter and aggregate in one script; return only what you need. Sandbox: ONLY network to the OpenAgenda API is allowed (no filesystem, env or subprocess); execution is killed after 5000 ms and heap is capped at 256 MiB.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。