athena-mcp-server

MCP日程管理

提供方 RLooney88

日程管理 stdio · 本地进程 OAuth 授权 社区 / 第三方 Cursor

Athena MCP Server is a small stdio adapter to Athena's existing HTTP API, providing core tools for tasks, projects, comments, deliverables, and search, suitable for MCP hosts to securely access and manage Athena data.

一句话选型结论

按资料字段整理

athena-mcp-server 属于日程管理类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Cursor,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类日程管理 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

日程管理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Local Deployment MCP Server API Adapter TypeScript Task Management Project Management Comment Management Search Athena

支持客户端

适用场景

Local DeploymentMCP ServerAPI Adapter

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程安排

按空闲时间自动排日程。

提醒与待办

设提醒、管待办清单。

时间协调

在多人之间找共同空档。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在日程管理场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
athena-mcp-server当前 未标注 stdio · 本地进程 本地部署 无 2026-10-16
Todoist MCP Server 79e800d2 35 stdio · 本地进程 支持远程部署 有 2026-05-17
Outlook Calendar MCP 7 stdio · 本地进程 本地部署 有 2026-05-18
MCP Server Apple Events 5 stdio · 本地进程 本地部署 有 2026-05-17
y-cli 未标注 stdio · 本地进程 本地部署 无 2026-10-05
Google Calendar 未标注 HTTP · 远程 支持远程部署 有 2026-05-17

服务器档案

日程管理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方RLooney88上游标注的维护方 RLooney88
分类日程管理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-10-16上游最后核验时间

详细介绍

5.8 KB
来自项目仓库与上游目录的原文,未做删改

Athena MCP server

A small stdio adapter to Athena's existing HTTP API. It has no database access, workflow engine, business rules, or automatic write retries.

Install and run

Requires Node 22+ and an Athena backend containing the API contract repair in docs/api-mcp-contract.md.```sh
npm ci
npm run build
cp .env.example .env

Set API_URL and ATHENA_API_KEY privately in .env.

node --env-file=.env dist/server.js


For an MCP host, configure **node** with absolute paths to `--env-file=/private/path/.env` and `/path/athena-mcp-server/dist/server.js`. Do not use `npm start` as the protocol command: npm can print lifecycle output to stdout. The node entry point emits only MCP protocol messages on stdout. Diagnostics use stderr.

The transport is stdio: the host starts one process. No separate public web server, PM2 daemon, Redis, or agent framework is needed. Remote hosts can use Athena's HTTP API directly; this package does not claim remote MCP/OAuth support.

## Credentials

- `API_URL`: backend origin, such as `https://api.example.com` (no `/api` suffix). HTTPS required outside loopback.
- `ATHENA_API_KEY`: a scoped key issued by Athena's existing Settings API-key management. Only a hash is stored there; existing revoke/rotate controls apply.
- `AUTH_TOKEN`: optional existing Athena JWT for six mobile-only compatibility tools, or JWT fallback for v1. API keys are never sent as mobile JWTs.
- `REQUEST_TIMEOUT`: milliseconds, default 30000, range 1..120000.
- Legacy `PROD_API_URL`/`TEST_API_URL` and `PROD_AUTH_TOKEN`/`TEST_AUTH_TOKEN` aliases are supported when NODE_ENV selects that environment. Prefer the single API_URL/ATHENA_API_KEY configuration.

Use the smallest required scopes: `tasks:read`, `tasks:write`, `comments:write`, `projects:read`, `clients:read`, `search:read`. Authentication and authorization are enforced by the API, not guessed by MCP. Keys are never printed by this adapter.

There is **no automatic mock mode**, including NODE_ENV=test. Tests explicitly start fixture HTTP servers or the disposable backend.

## Core v1 tools

- `athena_me`
- `athena_list_tasks`, `athena_get_task`, `athena_create_task`, `athena_update_task`
- `athena_add_comment`, `athena_get_comments`, `athena_create_deliverable`
- `athena_list_projects`, `athena_get_project`, `athena_list_project_stages`
- `athena_list_companies`, `athena_list_contacts`, `athena_search`

Tool discovery publishes the exact validated JSON schemas. Unknown fields are rejected instead of silently discarded.

### Writes and retries

Every core write requires `idempotency_key`: a caller-generated stable ID for **one intended action**. Reuse the same key and payload after a timeout. Do not generate a new key merely because the response was lost. Reusing a key with a changed payload returns 409.

`athena_update_task` also requires `expected_updated_at` copied exactly from `athena_get_task`. A stale version returns `stale_revision` (409). Read and reconcile the latest record before issuing a new intended update. MCP does not auto-fetch a newer version and overwrite it.

Task fields use the v1 contract: `title`, `project_id`, `client_id`, `stage_id`, `assignees` (UUID array), timezone-aware `due_date`, and priority `Low · Normal · High · Critical`. Status names remain backend/project-defined strings. Read project stages before setting stage_id.

Comments retain the MCP `content` argument and translate it to API `body`. Deliverables require a hosted HTTP(S) `url`; local file paths are not uploaded. Use Athena's existing upload flow separately before attaching a hosted file.

List responses retain API `data`/`meta.next_cursor`. Continue until next_cursor is null. Offset pagination is not a snapshot while records are changing.

### Existing mobile compatibility tools

The original `athena_create_subtask`, `athena_list_subtasks`, `athena_search_users`, `athena_get_categories`, `athena_approve_task`, and `athena_reject_task` remain available and explicitly labeled in discovery. They require AUTH_TOKEN because those operations do not have v1 equivalents. Subtask title is correctly translated to mobile `name`. Review actions use backend permissions; they do not invent status transitions.

These six calls **do not acquire the new v1 retry/revision guarantees**. The adapter never retries them automatically. Reconcile an uncertain write before retrying. Removing their existing capabilities or duplicating their business rules in MCP would be a larger, separate migration. Their mappings are tested; full live mobile workflows are not claimed verified by the v1 integration test.

## Compatibility changes from the old prototype

Core task/comment/deliverable tools now use `/api/v1` rather than `/api/mobile`. Replace old `assignee_id` with `assignees`, lowercase priorities with canonical priorities, flat work_for fields with project/client IDs, and task `category_id` with supported API fields only. `include_completed`/`needs_review` are not silently emulated on v1; use supported list filters. Reconnect/reload tool discovery after upgrading. Update calls need expected_updated_at and all core writes need idempotency_key. Fake-data runtime files and obsolete mock tests were removed.

## Verification```sh
npm test

This builds TypeScript and checks validation, configuration, request mapping, HTTP errors and a real SDK stdio handshake/tool call against a fixture HTTP server. The official MCP TypeScript SDK is pinned in the lockfile; the maintained 1.x API avoids an unrelated protocol migration.

For MCP → real Athena routes → PostgreSQL acceptance, follow Athena-Context/docs/api-mcp-contract.md. That suite runs discovery, concurrent create/retry, read-back, update/retry, stale rejection, cross-team rejection, pagination, comments and deliverables. It uses a disposable loopback PostgreSQL database and does not call providers.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
athena-mcp-server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

athena-mcp-server 怎么在 Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

athena-mcp-server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

athena-mcp-server 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

athena-mcp-server 支持哪些客户端?

资料标注支持 Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

athena-mcp-server 能提供哪些能力?

资料显示能力标签包括 Local Deployment、MCP Server、API Adapter、TypeScript、Task Management、Project Management。具体工具清单以官方文档为准。

athena-mcp-server 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

athena-mcp-server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-10-16。