Context

Name: Context
Author: honeycrisp-suite

by honeycrisp-suiteversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.honeycrisp-suite/context

Install

Overview

Description from the maker (original English)

Local-first personal context over MCP: mail/calendar metadata, briefings, person lookups. No cloud.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "context": {
      "command": "npx",
      "args": [
        "-y",
        "@honeycrisp/context"
      ]
    }
  }
}

Run this in your terminal

claude mcp add context -- npx -y @honeycrisp/context

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "context": {
      "command": "npx",
      "args": [
        "-y",
        "@honeycrisp/context"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "context": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@honeycrisp/context"
      ]
    }
  }
}

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.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account honeycrisp-suite, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2198 servers in this category
Published to the registry more recently than 22% of the other 2198 servers in this category
Basic checks equal to or better than 100% of the other 2198 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Context safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

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 Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago

Install

README from the maker

Open the README

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.

Cortland 🍎

Your agent brings the brain. Cortland brings the hands — and the human gate.

Give an AI real access to your Mac — Mail, Calendar, Reminders, Notes, files — without giving it the keys. Every consequential action previews first, waits for your approval through a channel the model can't touch, gets logged, and can be undone.

Cortland has no model of its own, no cloud, and no web access. That is the point. Whatever agent you already use — Claude, Codex, Cursor, or a local Gemma that never leaves the machine — gets a governed way to touch your real data and to reach you.

A worked example

An agent watched a handful of retailer pages for days, waiting for a limited-run controller to come back in stock. When it finally did — unattended, at an hour I was nowhere near my desk — my phone buzzed with an iMessage. I bought one.

Cortland never touched a website. It has no web-fetch tool and never has. The watching was done by a coding agent with internet access. Cortland was the part that reached me: on my own Mac, through Messages, with the recipient fixed in local config so nothing the agent generated could point that message at anyone else.

That division is the pitch in one story. Your agent has the reasoning and the internet. Cortland has your Mac, your Apple apps, and your attention — and every outward action still stops to ask.

The part worth telling

The first version cheated, and I only found out by reading my own audit log.

No governed "tell the human" tool existed. The iMessage bridge could *answer* me, but nothing could start a conversation — so the monitor imported Cortland's send module directly and called it. It worked, and it was genuinely Cortland doing the sending: same owner handle from config, same AppleScript escaping, same hourly rate cap. But it went *around* the framework instead of through it, so days of running left zero audit rows.

That is this project failing its own test. A guarantee with no legitimate path through it is a guarantee people route around — and the person who routed around it was the one who wrote the guarantee.

The fix is notify_owner: write-safe, because a message to you is not an outward action, it *is* the review loop. It has no recipient argument at all — the handle comes from local config, so no model output and no injected content can redirect it. Its hourly cap is counted from the audit log rather than from memory, so a cron job that starts fresh every run still can't exceed it. A notification now leaves a row behind. This one is real, copied out of the audit DB after sending a test message to my own phone:

notify_owner | Messages | write-safe | undo=none | dry_run=0 | ok

principal: cli:notify tool_version: 0.2.0 args: {"text":{"redacted":true,"length":84,"sha256":"3e389e33…"}, "source":"cortland-test"}

The body is stored as a length and a hash — the row proves a message was sent without keeping what it said. source stays readable because it is a label, constrained to a slug, and not content anyone can compose.

What it looks like in use

Text it like a contact — the bridge, answered by a 4 GB model on an 8 GB MacBook Air. Nothing left the Mac:

You:       Add a reminder to call the vet tomorrow at 2pm

Cortland: Received — working on it… Cortland: Added "Call vet" for tomorrow, Aug 3 at 2:00 PM.

The texting interface needs a second Apple ID, signed into Messages on the Mac only — a mouthpiece, not a worker. It owns no mail, no calendar, no data. You text it from your phone like any contact; the Mac still does the work as *you*. Your system iCloud stays yours. Claude Code, Cursor, Codex, and other MCP clients skip this step: they talk to the same tools over stdio.

Ask about your week — reads are free, no approval needed:

You:       Anything from the school this week?

Cortland: Three emails from Lincoln Elementary. Two are the weekly newsletter; one from Ms. Alvarez on Tuesday asks for a permission slip by Friday.

Ask it to change something — writes stop and ask, every time:

The code in that prompt is generated by the framework and never enters the model's context — so even a fully prompt-injected model can't forge your approval. Ignore the message and the action expires, refused.

Ask what it can do — answered from the tools actually installed, so it can't overclaim:

You:       what can you do?

Cortland: Here's what I can do with your Mac: • Calendar: list, look up, create, delete • Mail: search, read, follow threads, draft, send (asks first), flag, file • Notes: search, read, create, add to • Reminders: list, search, create, tick off, delete

Anything that deletes or changes things asks you first — I text you a code and wait for "yes ". Reads just happen.

In Claude Code or Claude Desktop, the same tools are just there:

You: send a reply to Ms. Alvarez saying the slip is coming Thursday

Claude: *[searches mail, reads the thread]* I can send this from your

Personal account to alex@example.com. Approve in the usual channel.

mail_send is write-gated. Live mode plus per-action human approval. A stolen token can only *ask*.

Requirements

macOS only. Nothing here runs on Windows or Linux — the tools talk to Apple apps via Automation.

	Minimum	Comfortable
OS	macOS 13 Ventura	macOS 15+
Mac	Any Mac that runs Ventura (Intel can drive Cursor/Claude)	Apple Silicon (M1 or newer)
Node	20 LTS (`node -v`)	22
Toolchain	Xcode Command Line Tools (`xcode-select -p`)	same — `better-sqlite3` compiles native code
Client	One MCP app: Cursor, Claude Code, Claude Desktop, Codex, or LM Studio	plus Ollama if you want to text it
RAM	8 GB (cloud/Cursor model, or Gemma 4 E2B)	16 GB+ for larger local models
Disk	~500 MB for this repo’s build	+6 GB if you pull `gemma4:e2b-it-qat`
Apple apps	The apps you want touched, signed in as you	Mail + Reminders is the usual first pair

iMessage bridge only: macOS 13+ (modern chat.db), Full Disk Access for the process that runs Node, Automation → Messages, and a second Apple ID signed into Messages.app — not into System Settings. See SETUP.md §5.1.

Osaurus as a client: Apple Silicon, macOS 15.5+.

Not required: a developer account, iCloud for Path A, or any API key.

Quick start

Fastest path to “it searched my mail” — Cursor (or Claude Code) as the brain, no second Apple ID, no Ollama:

xcode-select --install          # if `xcode-select -p` fails

git clone https://github.com/cortland-suite/cortland.git cd cortland npm install && npm run build # first install compiles sqlite — a minute

Then Cursor Settings → MCP, add servers pointing node at packages/mail/dist/server.js (and reminders/notes/calendar if you want them). Absolute paths. JSON is in [docs/08_local_models.md](docs/08_local_models.md#cursor).

Ask: *search my mail for anything from school this week.* macOS will prompt Automation (Cursor → Mail). Allow it.

Writes stay previews until you set "live": true in ~/Library/Application Support/cortland/config.json. Even then, send/delete asks you per action.

Texting it from your phone is a longer path (second Apple ID + Ollama). SETUP.md is the ordered list; docs/08 is the illustrated one.

Why it exists

Most MCP servers for personal data are thin wrappers around AppleScript: delete_email, send_message, executed the instant a model calls them. That's a hard thing to trust with an inbox, and the alternatives don't help — cloud assistants (Poke, Arlo, Lindy) can't touch Apple-native data at all, because Apple gives them no API, and self-hosted agents like OpenClaw run ungoverned (a CVSS 8.8 in January 2026, with permission gates still on the roadmap).

Cortland inverts the default. A tool call *previews* what it would do unless you've opted into live mode, and even then every consequential action waits for you. The framework enforcing that is a small library with a test suite proving each guarantee can't be bypassed — and every tool in the suite is built on it.

The guarantees


Dry-run by default	Gated tools preview instead of executing. Every config error resolves toward dry-run.
The human gate is out-of-band	Approval arrives via a native dialog, a file you move, your client's own UI, or a text you reply to — never through model text.
Everything is audited	Success, failure, dry-run, denial, refusal: one local SQLite row each. "What did my tools actually do?" always has an answer.
Undo is enforced at registration	A tool claiming native undo must produce a recipe before the write, or the framework refuses it.
Content is data, not instructions	Everything read from mail, notes, or messages returns inside a nonce-delimited fence.
Safety by absence	No ungated send. No attendee invitations. No reading conversations other than your own.
Local-first	No accounts, no credentials, no cloud. Your model, your machine, your disk.

Install

From the repo:

git clone https://github.com/cortland-suite/cortland.git

cd cortland npm install npm run build npx cortland setup

The wizard asks before every step and records what it did. Full walkthrough — including the iMessage bridge, permissions, and model choice — in [SETUP.md](SETUP.md). Connecting Cursor, Codex, LM Studio, Osaurus, or Ollama: [docs/08_local_models.md](docs/08_local_models.md).

Packages

Package	What it does
`@cortland/governed`	The framework: dry-run defaults, approval gates, audit, provenance, undo, injection fencing. Build your own governed tools on it.
`@cortland/mail`	Apple Mail: read, search (two tiers), threads, drafts, send (write-gated).
`@cortland/reminders`	Reminders: lists, search, create, complete, delete — with native undo.
`@cortland/notes`	Notes: folders, search, read, create, append.
`@cortland/calendar`	Calendar: window queries, create, delete. Cannot send invitations, by design.
`@cortland/context`	Local context layer: mail/calendar metadata (pointers, never bodies), briefings, person lookups, a corrections flywheel.
`@cortland/imessage`	Text your own AI. Second Apple ID in Messages (mouthpiece only); owner-only by construction, approvals by reply, plus `notify_owner` so an unattended agent can reach you first.
`@cortland/folders`	Folder-as-API: drop a file in iCloud from any device, a declared local pipeline runs.
`@cortland/remote`	Reach the suite from your other devices over your own private network.
`@cortland/setup`	The onboarding wizard.

Bring your own model

Cortland is the tools. You pick the brain.

Path A. Cursor, Claude Code, Claude Desktop, Codex, LM Studio, or Osa

Only the beginning is shown; read the rest in the repo

Context

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

Cortland 🍎

A worked example

The part worth telling

What it looks like in use

Requirements

Quick start

Why it exists

The guarantees

Install

Packages

Bring your own model