Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Project management for AI agents: tasks, docs, decisions and time in one shared team context.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.frameonlab.com/api/v1/mcp在终端中运行这条命令
claude mcp add --transport http frameon https://api.frameonlab.com/api/v1/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"frameon": {
"url": "https://api.frameonlab.com/api/v1/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"frameon": {
"type": "http",
"url": "https://api.frameonlab.com/api/v1/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.frameonlab.com/api/v1/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 frameonlab.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.2.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for agentic project management. Tasks, documents, decisions and time in one shared team context, reachable by an AI agent over the Model Context Protocol.
This repository holds the public surface of that server: the protocol types, the guide the server serves to connected clients, the skill playbooks, and the published manifest. The server itself is hosted — you do not run it.
| Endpoint | https://api.frameonlab.com/api/v1/mcp |
| Transport | streamable-http |
| Auth | OAuth 2.1 — Dynamic Client Registration, PKCE (S256) required |
| Tools | 20 (13 read-only, 7 write) — see docs/tools.md |
| Registry | com.frameonlab/frameon |
| Docs | https://app.frameonlab.com/mcp |
An AI assistant asked to help with a project normally works from whatever got pasted into the chat. It cannot see what was decided three weeks ago, which constraint someone stated in a meeting, or who is already on the task. So it guesses, confidently, and a human spends the afternoon correcting it.
FrameOn exposes the project itself: the task tree, the wiki where decisions live, a separate project memory holding conventions and traps, the team, the alerts and the time log. The agent reads the real state, writes back what it did, and the next agent — on another machine, in another client — finds it there.
claude mcp add --transport http frameon https://api.frameonlab.com/api/v1/mcp
mcpServers clients{
"mcpServers": { "frameon": { "type": "http", "url": "https://api.frameonlab.com/api/v1/mcp" } } }
Add a connector pointing at the same URL. The OAuth flow runs in the browser; no key is pasted anywhere.
There is no API key in any of these. The first call opens an authorisation screen, a human approves the workspace, and the client stores a token it rotates on its own. A Personal Access Token also works, as Authorization: Bearer …, for scripted use where no browser exists.
More, including a per-client walkthrough: https://app.frameonlab.com/mcp
Connect and call frameon://guide. The server hands back a written briefing — what FrameOn is, which tool answers which question, the traps that cost a round-trip, and, just as importantly, what FrameOn has that the agent does not: the Gantt, the approval step on timesheets, the financial reports. A tool that refuses to say where its edges are gets improvised around, badly.
| Path | What it is |
|---|---|
src/mcp.types.ts | JSON-RPC 2.0 envelope types and the protocol versions the server echoes |
src/mcp-guide.ts | the text served at frameon://guide, plus the prompt specs |
src/mcp-skills.ts | the skill playbooks behind list_skills / get_skill |
.mcp.json | drop-in client config at the repo root — the Open Plugins entry point |
server.json | the manifest published to the MCP registry |
docs/tools.md | the 20 tools, with the descriptions the server advertises |
examples/ | client configuration, ready to paste |
The service implementation, the database and the tenant layer are not here and are not open source. What is here is what a client talks to and what an agent reads — enough to know exactly what you are connecting to before you connect.
The endpoint is multi-tenant and every query filters by tenant. A credential reaches the projects its role reaches and nothing else; tenant_id never appears in a tool response. Write tools are gated per call, on the scope and the role carried by the credential — never on anything sent in the request body.
Found something that looks wrong? seguranca@frameonlab.com. Please do not open a public issue for a suspected vulnerability.
MIT — see LICENSE.