Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Readiness checks, a paid Fix Pack, TaskMarket reads, and caller-declared funnel evidence.
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://samedaydesk.com/mcpRun this in your terminal
claude mcp add --transport http task-evidence https://samedaydesk.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"task-evidence": {
"url": "https://samedaydesk.com/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": {
"task-evidence": {
"type": "http",
"url": "https://samedaydesk.com/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://samedaydesk.com/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 samedaydesk.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.0) reached the registry 28 days 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.
Public helpers for free discovery and offline result reuse. Node 22.x. The commands below use plain ESM under tools/; no npm install is required.
Start with the examples below, then open the helper documentation for options and error handling.
| Doc | Purpose |
|---|---|
| tools/presence/FOR-AGENTS-COLD-READ.md | Free discovery when apex TLS/connect fails |
| tools/presence/REGISTRY-CONSUMER.md | MCP Registry version=latest pitfall |
| tools/result-reuse/README.md | Offline source → task-memory observation |
| tools/offer-routing/README.md | Task → existing SameDayDesk/Neomorphic offer |
| tools/offer-routing/capability-limits-matrix.json | Machine-readable capability/limits matrix |
Live free catalogs (no pay): https://agents.samedaydesk.com/llms.txt and https://agents.samedaydesk.com/.well-known/skills/index.json. Apex https://samedaydesk.com/for-agents may TLS/connect-fail; cold-read falls back to those alternates.
| Mode | Network | Payment | How |
|---|---|---|---|
| Offline fixture cold-read | none | none | preferFixture: true → outcome: "offline_fixture" |
| Live cold-read | free HTTP only | none | default resolve → often alternate_live when apex fails |
| Result-reuse preview/export | none (local JSON) | none | fixtures + --opt-in to write |
These helpers do not require a purchase. Paid extract/batch routes are separate.
From the repository root (no install):
node --input-type=module -e 'import {resolveForAgentsColdRead} from "./tools/presence/for-agents-cold-read.mjs"; console.log(JSON.stringify(await resolveForAgentsColdRead({preferFixture:true}), null, 2))'
Expected: outcome: "offline_fixture", paid: false, liveObserved: false.
node --input-type=module -e 'import {resolveForAgentsColdRead} from "./tools/presence/for-agents-cold-read.mjs"; console.log(JSON.stringify(await resolveForAgentsColdRead(), null, 2))'
Expected when apex transport fails but agents.* respond: outcome: "alternate_live", paid: false.
PILOT_EXAMPLE_DIR="$(mktemp -d)"
NOW="$(date -u +%Y-%m-%dT%H:%M:%SZ)" node tools/result-reuse/cli.mjs preview \ --input tools/result-reuse/fixtures/accepted-page-change.json \ --task-id vendor-watch --subject vendor-page-result --sequence 1 --clock "$NOW"
node tools/result-reuse/cli.mjs export \ --input tools/result-reuse/fixtures/accepted-page-change.json \ --task-id vendor-watch --subject vendor-page-result --sequence 1 --clock "$NOW" \ --opt-in --out "$PILOT_EXAMPLE_DIR/reuse-observation.json" printf 'Saved example in %s\n' "$PILOT_EXAMPLE_DIR"
Record-kind fixture:
PILOT_EXAMPLE_DIR="$(mktemp -d)"
NOW="$(date -u +%Y-%m-%dT%H:%M:%SZ)" node tools/result-reuse/cli.mjs export \ --input tools/result-reuse/fixtures/accepted-record-report.json \ --task-id vendor-watch --subject record-export --sequence 1 --clock "$NOW" \ --opt-in --out "$PILOT_EXAMPLE_DIR/reuse-record-observation.json" printf 'Saved example in %s\n' "$PILOT_EXAMPLE_DIR"
Expected written observation: schema: "neomorphic.task-memory.observation.v1"; export requires --opt-in plus caller clock/task/subject/sequence.
When the job is known, route with the matrix before paying or treating a sample as live:
node tools/offer-routing/route-job.mjs tools/offer-routing/fixtures/complete-issue-discussion.job.json
Expected: ok: false, selected: null, exit code 2 and complete_issue_acquisition_unavailable. Neither paid /extract nor task-kit packaging acquires a complete discussion. This matrix does not advertise the pending issue-evidence acquisition pack. For historical fixture composition use fixtures/supplied-issue-brief.job.json under tools/offer-routing/. The MoltJobs SDK pack runs a disposable local HTTP rehearsal; its shipped runner refuses --live, even with credentials. Hosted archives are downloads, not hosted job execution. Routing does not evaluate acceptance criteria or authorize payment.
npm run test:public-entry
That script runs the offline cold-read and fixture export commands cited above (no network, no payment). Existing focused suites: npm run test:presence, npm run test:result-reuse, npm run test:offer-routing.