granttap-mcp weekly downloads statistics

GrantTap MCP

See what your coding agents are doing. Step in when they need you.

GrantTap connects local Claude Code and Codex work to a live control center on Mac, iPhone, iPad, and Apple Watch. See the Task and its latest activity, answer an approval or question with context, and continue the same goal as sessions or computers change. Cursor and Grok Build join the view where their local integrations support it.

This repository supplies the local runtime: CLI, MCP server, provider hooks, adapters, and wire contracts. It powers Project Mesh, Governance, and observed usage while agents and provider credentials stay on your computer. Controller traffic is end-to-end encrypted.

Known chats are read from their published native identities, without another walk through every provider log. The local helper retains a private metadata index so a restart can send current heads of the saved Now chats before a fresh discovery scan. The Apple clients keep downloaded conversations, pictures, and Mesh data locally for offline use; clearing that cache preserves the account login.

The chat's Files pill opens recorded changes for the current reply and the Task's All files tree. Directory and text reads are paged, encrypted for the requesting controller, and restricted to that native execution's admitted checkout. Received previews remain on the device for offline inspection. Agents opens nested execution conversations within the same Task.

Messages sent to a chat open in Codex Desktop continue that same conversation, including while a turn is running. The runtime forwards them to the existing desktop owner and preserves the delivery ID across retries. Pause reaches that owner too. A provider acceptance receipt means Codex accepted the message; its answer then arrives through the existing chat history. Relay storage is a separate stage.

The MCP runtime, plugins, and CLI use the GrantTap Commercial Source License. Managed service use requires authorized GrantTap account access; official TestFlight access remains free. Earlier releases through 0.8.75 retain their Apache-2.0 permissions. The Apple apps, Engine, relay, and website have their own terms.

Website · npm · Security model · Relay source

Start here

• Connect your computer and devices
• Choose a connection mode and plan
• Provider support
• Install provider integrations
• Messages, queues and decisions
• Project Mesh and task transfer
• Approvals and questions
• Security and relay boundary
• Troubleshooting and help
• License

Plans and what you pay for

Planned US prices for the first commercial release:

Plan	Monthly price	Managed publishing computers
Personal	$4.99	2
Personal Plus	$7.99	5
Fleet	$13.99	15

The same core GrantTap features are included in every monthly plan. A computer running several supported agents still uses one publishing-computer seat. iPhone, iPad, Apple Watch and Macs used only as controllers do not use additional execution-computer seats. Fleet is a larger personal allowance, without an enterprise SLA or a per-person license.

An eligible new Apple subscription starts with 7 days free, then renews monthly at the price shown by Apple. To avoid renewal, cancel at least 24 hours before the trial ends in Apple's subscription settings. A local cache is not deleted when managed access ends.

Official TestFlight builds include all features without a purchase or subscription. A trial and TestFlight access are different forms of access. Paid products are still being prepared for commercial launch; the App Store purchase sheet determines availability, localized prices, eligibility and terms. Models, AI tokens and coding-provider plans are purchased separately.

Mac Local is a separate $39.99 one-time purchase for local control and an own relay. Hosted managed delivery is not included in that purchase. An active Personal subscription already covers a managed Mac client; both purchases are not required for the same managed mode. npm distributes the computer runtime; it does not sell an independent subscription or unlock a hosted entitlement.

See current pricing, terms and Help / FAQ.

Messages, queues and decisions

1. The controller encrypts the message or decision and submits it to the relay.
2. A relay storage receipt confirms that the relay saved it durably. The computer can be asleep or offline at this point.
3. The computer receives the packet when connected, routes it to the intended Task/execution and reports provider acceptance, failure or a required decision.
4. The provider's answer returns through the existing conversation.

A saved message does not mean the agent has started. Queue and delivery stages remain distinct; bounded storage, retention, access checks and service limits can reject a submission with an explicit error. A controller does not need to wait for the execution computer before showing a confirmed relay save.…