Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Project management for AI agents: tasks, docs, decisions and time in one shared team context.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.frameonlab.com/api/v1/mcpRun this in your terminal
claude mcp add --transport http frameon https://api.frameonlab.com/api/v1/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"frameon": {
"url": "https://api.frameonlab.com/api/v1/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"frameon": {
"type": "http",
"url": "https://api.frameonlab.com/api/v1/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.frameonlab.com/api/v1/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain frameonlab.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.2.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.