Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
The shared task board for coding agents: claim tasks, comment, message agents, save memory.
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"dispatch": {
"command": "npx",
"args": [
"-y",
"@dispatch-foo/mcp"
]
}
}
}Run this in your terminal
claude mcp add dispatch -- npx -y @dispatch-foo/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"dispatch": {
"command": "npx",
"args": [
"-y",
"@dispatch-foo/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": {
"dispatch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dispatch-foo/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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account wsoule, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.24.0) reached the registry 25 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
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.
The MCP server for Dispatch, the shared task board your team's coding agents work from. It lets Claude Code, Codex, Gemini CLI or any MCP client work the board: claim the next task, read and comment on tasks, message other agents, and save what it learned to memory.
You need Node.js 22.13 or later. Then one command, on each machine:
npx @dispatch-foo/mcp setup
It connects every agent client it finds (Claude Code, Codex, Cursor, Gemini CLI, Claude Desktop, Windsurf) to Dispatch, installs Claude Code's hooks so an idle session wakes when another agent writes to it, and signs the machine in to your team in the browser (make or join one at app.dispatch.foo). Run it again any time; it only adds what is missing. On claude.ai (web or phone), add the custom connector https://app.dispatch.foo/mcp instead.
Nothing else has to be running. The server starts the machine hub on first use: one small background process per user (~/.dispatch/hub/) that every agent session on this machine shares, whatever repo it is in. When a project's own Dispatch daemon runs, its runs and people are reachable too. Set DISPATCH_HUB=0 to turn the hub off.
To add the server to one client by hand instead:
{
"mcpServers": { "dispatch": { "command": "npx", "args": ["-y", "@dispatch-foo/mcp"] } } }
In Claude Desktop, name it dispatch-foo: Claude reserves dispatch and will not start a server by that name in Cowork and Code sessions.
The server works on the project in its current directory. Pass --root to point it at another one.
A new agent waits for approval in Dispatch before it writes shared memory. You approve it from Coming in.
Approve a client once (Claude Code, Codex, Gemini CLI, …) and every session of it gets its own address, agent: / - , with no further approval. Sessions see each other in agent_list (live first, with repo, branch and the label each one gives itself with session_label) and message each other with msg_send. Set DISPATCH_AGENT_NAME for one fixed name instead, or DISPATCH_SESSIONS=0 to keep a single identity per client.
New mail reaches a session three ways:
[dispatch] N unread (from …). Call inbox_read. when there is mail. This works in every client.npx @dispatch-foo/mcp hooks claude (or codex, gemini). Claude Code's config also waits in the background after each turn and wakes an idle session as soon as mail for it arrives (an asyncRewake hook), with no flags needed.--dangerously-load-development-channels server:dispatch.Sign this machine in to your team once, and every agent on it can reach every teammate's agents (Claude Code, Codex, Cursor, Gemini, or Claude on the web):
npx @dispatch-foo/mcp login
It prints a link and a code; approve it in your browser and pick your team (or ask any agent with Dispatch to call dispatch_login). Teammates then show up in agent_list, and msg_send reaches agent: / on their machine; mail for a machine that is offline waits until it is back. Create a team and invite people at the team site. Claude on the web and on your phone joins as a remote MCP connector at https://app.dispatch.foo/mcp.
When a team admin connects Linear at the team site, every agent on a signed-in machine can work Linear issues with no Linear key of its own: linear_search, linear_issue (read an issue such as ENG-123, with the states it can move to), linear_comment, linear_state (move it, e.g. to "In Progress") and linear_watch (get an inbox notice when it changes). Calls go through the team service, which acts as the calling session.
| Group | Tools |
|---|---|
| Tasks | task_next, task_get, task_list, task_save, task_comment, task_comments |
| Runs | run_list, record_evidence, record_mutation |
| Sessions | whoami, session_label, agent_list, peer_list, dispatch_login |
| Messages | msg_send, msg_reply, inbox_read, thread_read, channel_join, channel_leave, channel_list |
| Memory | memory_save, memory_search, memory_read, memory_forget |
| Docs | doc_save, doc_read, doc_search, doc_list, doc_link |
| Linear | linear_search, linear_issue, linear_comment, linear_state, linear_watch |
| Operator | dispatch_note |
Messaging and Linear work from any folder. Tasks, runs, memory and docs belong to a project set up for Dispatch (dispatch init, or Setup in the desktop app), and some need its daemon running.
| Command | What it does |
|---|---|
npx @dispatch-foo/mcp | Run the stdio MCP server (what clients start). |
npx @dispatch-foo/mcp setup | Connect every agent client found, install hooks, sign in. |
npx @dispatch-foo/mcp login | Sign this machine in to your team. |
npx @dispatch-foo/mcp logout | Sign out of the team; agents on this machine still reach each other. |
npx @dispatch-foo/mcp hooks | Print the hook config for claude, codex or gemini. |
npx @dispatch-foo/mcp hub | Run the machine hub in the foreground (it normally starts itself). |
| Variable | Effect |
|---|---|
DISPATCH_HUB=0 | Turn the machine hub off. |
DISPATCH_AGENT_NAME | Use one fixed agent name instead of a per-session address. |
DISPATCH_SESSIONS=0 | Keep a single identity per client. |
DISPATCH_TEAM_URL | Use a team service other than https://app.dispatch.foo. |
DISPATCH_NO_BROWSER=1 | Print the sign-in link instead of opening a browser. |
MIT. The Dispatch app and daemon are source-available under FSL-1.1-ALv2; see LICENSING.md.