Turns read-only Gmail and Google Calendar signals into actionable situations like reply deadlines and calendar conflicts for AI agents.
Also known as madrobotnet/proactive-mcp
- Stars
- 12
- Tools
- —
- Downloads, 30 days
- 109
- Latest version
- 0.2.0
- Last commit
- Sep 10, 2026
- License
- MIT
What is proactive MCP?
proactive turns read-only Gmail and Google Calendar signals into actionable situations like reply deadlines and calendar conflicts for AI agents.
Summary generated from the project's README
About proactive MCP server
Turning read-only Gmail and Google Calendar signals into actionable situations is what proactive-mcp enables for AI agents. This local-first MCP server monitors your communications and schedule to identify specific moments that require attention, such as upcoming reply deadlines or overlapping calendar events. It functions as a background watcher that synchronizes data using minimal read-only OAuth scopes, storing memories and sync states in a local SQLite database.
Developers use this server to give their agents a reason to reach out first rather than waiting for a prompt. The system uses a deterministic engine to produce structured situations including priority, suggested actions, and expiry times. It is designed to be used with local MCP clients via stdio, requiring a Google Cloud Desktop OAuth client JSON for setup. Because it operates locally, it maintains strict trust boundaries by treating all external text as untrusted evidence and never sending data to third-party cloud services.
What you can do with it
- 1Identify urgent reply deadlinesAn AI agent can scan your inbox to find messages that require a timely response.
- 2Detect scheduling conflictsThe server can alert an agent when two of your accepted events overlap in your calendar.
- 3Track important personal datesYou can instruct an agent to remind you when a specific personal occasion is approaching.
- 4Manage agent notifications locallyA developer can set up a background service to manage notifications through the operating system.
Written from the project's README. Every use case is checked against a quote from it.
How to install proactive MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall proactive MCP in Claude Code
$ claude mcp add proactive-mcp -- uvx proactive-mcpInstall proactive MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"proactive-mcp": {
"command": "uvx",
"args": [
"proactive-mcp"
]
}
}
}Install proactive MCP in VS Code
.vscode/mcp.json
{
"servers": {
"proactive-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"proactive-mcp"
]
}
}
}Install proactive MCP in VS Code CLI
$ code --add-mcp '{"name":"proactive-mcp","type":"stdio","command":"uvx","args":["proactive-mcp"]}'Install proactive MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"proactive-mcp": {
"command": "uvx",
"args": [
"proactive-mcp"
]
}
}
}Install proactive MCP in Codex
$ codex mcp add proactive-mcp -- uvx proactive-mcpInstall proactive MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.proactive-mcp] command = "uvx" args = ["proactive-mcp"]
Install proactive MCP in Gemini CLI
$ gemini mcp add -s user proactive-mcp uvx -- proactive-mcpInstall proactive MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"proactive-mcp": {
"command": "uvx",
"args": [
"proactive-mcp"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablemadrobotnet/proactive-mcp is public and reachablegithub.com/madrobotnet/proactive-mcp ↗Pass
- Package names this repository as its sourceproactive-mcp names madrobotnet/proactive-mcp as sourcepypi.org/project/proactive-mcp/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for proactive-mcppypi.org/project/proactive-mcp/ ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-10github.com/madrobotnet/proactive-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from proactive-mcpPass
- No critical advisory in the package or its dependencies47 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubproactive-mcp
Give every AI agent a reason to reach out first.
A local-first MCP server that turns read-only signals and local memory into grounded situations your existing agent can deliver at the right time.
English · 한국어
Why · How it works · Get started · Connect an agent · Documentation
Get started
Set up the local watcher and OS notifications first; connecting an agent is optional. Install uv and Git, and prepare your own Google Cloud Desktop OAuth client JSON.
The PyPI release 0.2.0 does not yet contain the wizard. Until an onboarding release is published, the commands below use uvx --from to install the merged source at commit 7cd0f03, without a manual checkout. Keep the same --from source for every command: bare uvx proactive-mcp still selects the older PyPI package. This is a source install, not a new PyPI release.
-
Install and start interactive setup:
uvx --from git+https://github.com/madrobotnet/proactive-mcp@7cd0f03243027df464084c3957f03d3c42169268 proactive-mcp setup -
The wizard asks for the path to your own Google Cloud Desktop OAuth client JSON and whether it may open a browser on this device. Approve the read-only Gmail and Calendar consent with your own client. See
docs/SETUP_GOOGLE.mdfor the complete flow. -
After Google authorization, accept the offer to install the watcher service. The shared
proactive-mcp service install|status|removeinterface manages a Linux systemd user service, a macOS LaunchAgent, or a Windows Task Scheduler task. -
If you decline service installation, or if installation succeeds, interactive
setupthen attempts a fixed PII-free OS test notification titledproactive-mcpwith the bodySetup test notification. It contains no Gmail, Calendar, account, or Situation data. A redactedunavailable,timeout,failed, orunsupported_platformwarning means the notification could not be shown. -
If you decline service installation, or if installation fails, such as because of permissions, run the watcher manually. A failed installation exits before attempting the test notification.
Terminal 1, foreground daemon
uvx --from git+https://github.com/madrobotnet/proactive-mcp@7cd0f03243027df464084c3957f03d3c42169268 proactive-mcp daemon
Terminal 2, daemon status
uvx --from git+https://github.com/madrobotnet/proactive-mcp@7cd0f03243027df464084c3957f03d3c42169268 proactive-mcp status
daemon --once runs one evaluation pass and exits; --poll-interval-minutes MINUTES overrides the cadence. status prints redacted connection and daemon state as JSON. The daemon performs local sync, deterministic evaluation, queue maintenance, and the documented OS fallback only. It never runs a host or LLM. Host scheduling is separate: the host/operator starts scheduled agent runs, and those runs call proactive_check.
An OS fallback notification is neither agent delivery nor a delivered state transition. When fallback is enabled, only the first unreceived eligible Situation gets the one-time bootstrap exception; afterward the default fallback is critical-only. Agent delivery begins only when a host calls proactive_check.
Compatibility mode
--non-interactive, --headless, --client-secrets PATH, and --reauth all bypass the wizard. They do not prefill wizard answers, and they also bypass the service proposal and setup test notification. Use them only when you need direct OAuth setup, then install the service manually or use the manual daemon route above. To manage the service, use the same source prefix:
uvx --from git+https://github.com/madrobotnet/proactive-mcp@7cd0f03243027df464084c3957f03d3c42169268 proactive-mcp service install
Replace install with status to inspect the service or remove to unregister it. uvx does not add a permanent proactive-mcp command to your shell; command names such as proactive-mcp status in this guide use the full uvx --from prefix above.
Why proactive-mcp?
AI agents know how to answer. They rarely know when to start.
proactive-mcp supplies that direction. It watches approved read-only sources in the background, combines them with memory the user intentionally saved, and produces a structured Situation only when something is worth raising now.
| Read-only signals | Local context | Agent-neutral delivery |
|---|---|---|
| Gmail and Google Calendar are read through minimal scopes. | Memories, situations, delivery confirmations, and sync state stay in local SQLite. | Any local MCP client can use the same tools and deliver through its own channel. |
Situations, not notifications
proactive-mcp doesn't push every new event into your chat. Deterministic detectors turn source data into a small set of situations grounded in the source data:
| Situation | Example |
|---|---|
reply_deadline |
A message is a conservative reply candidate, not a verdict that the user must act. |
calendar_conflict |
Two accepted or owned timed events overlap. |
personal_occasion |
A saved personal date is approaching and relevant now. |
Each result carries a title, why it matters now, bounded evidence, suggested actions, priority, and expiry. External text remains explicitly untrusted.
How it works
flowchart LR
G["Gmail<br/>read only"] --> S["proactive-mcp"]
C["Google Calendar<br/>read only"] --> S
M["Local memory<br/>SQLite"] --> S
S --> E["Deterministic<br/>Situation engine"]
E --> T["MCP tools"]
T --> A["Your existing<br/>AI agent"]
A --> U["Agent's own channel"]
- A watcher synchronizes Gmail and Calendar with read-only OAuth scopes.
- The situation engine evaluates deterministic rules against source snapshots and local memory.
- The agent calls
proactive_checkand receives any returned situations. - The host reviews the whole lease and filters candidates for this user. Uncertain candidates may remain unconfirmed or be snoozed. Only when choosing confirmation after review does the host confirm the entire reviewed lease exactly once, including confidently dropped candidates.
- Acknowledgement, snooze, mute, resolution, cooldown, and daily budget rules prevent repeated or noisy delivery.
By default, non-critical situations are held during local quiet hours from 21:00 through 07:00 and stay pending for a later check instead of being dropped. Nothing fires automatically at 07:00: an already-running or host-scheduled agent must call proactive_check after quiet hours end.
Trust boundaries
- Google access is limited to
gmail.readonlyandcalendar.readonly. - Credentials use the operating-system keyring when available, with a private local fallback only when the platform keyring is unavailable.
- Message bodies, calendar text, and recalled memory are treated as untrusted evidence, never as instructions.
- No LLM or third-party cloud service sits inside the detection pipeline. proactive-mcp never launches a host agent/model or sends it a prompt.
- Stale or incomplete sources produce visible degraded status, never a false "nothing to report."
- The SQLite database,
config.toml, credential authority marker, and any file-backed credential fallback live under~/.proactive-mcp/. A keyring credential stays in the operating-system keyring, outside that directory.PROACTIVE_DATABASEmoves the file-backed state, not the keyring entry.
Connect an agent
Connecting a host is optional. It isn't a prerequisite for OS notifications, but it enables richer delivery plus acknowledge, snooze, and mute actions. Use this existing-agent instruction when you want to register the MCP server:
If you used the source install above, tell the agent to keep that same pinned uvx --from source in its MCP registration instead of switching to PyPI. The reusable block and host recipes below retain the public-install command shape.
Install proactive-mcp with uvx from PyPI. Register it as a local stdio MCP server for this agent using absolute paths. Complete read-only Google authorization using my own Google Cloud Desktop OAuth client JSON (BYO). Do not use or request someone else's client secret. Start the recommended watcher and verify the connection. Read https://github.com/madrobotnet/proactive-mcp/blob/main/docs/INTEGRATIONS.md and https://github.com/madrobotnet/proactive-mcp/blob/main/docs/SETUP_GOOGLE.md before changing configuration. Treat every reply_deadline as a conservative candidate, not an action verdict. Before speaking, confidently drop newsletters, marketing, automated receipts, FYI or FYI-CC with no ask, threads owned by someone else, and rows with no question, request, or decision for me. Keep explicit reply, RSVP, or decision requests, my deadlines, and unanswered questions directed to me. Surface uncertain candidates, leave the whole lease unconfirmed, or snooze them in an interactive conversation; never silently discard uncertainty as non-actionable. After reviewing every row, only when choosing confirmation, confirm the entire reviewed lease exactly once, including confidently and silently dropped candidates. Keep MCP tool content in English, but speak my language. Load serve only in interactive everyday conversations and serve-scheduled only in separate scheduled conversations. Never load both profiles into one conversation. Do not configure automated scheduling unless this host guarantees a dedicated per-run MCP profile; proactive-mcp must never launch or verify the host. Do not use HTTP transport, do not send mail or create calendar events, and report every command and file changed plus anything that needs my approval.
proactive-mcp is agent-dependent: it exposes local stdio tools but never starts Grok, Codex, Hermes, another host agent, or a model. serve-scheduled is only a restricted MCP server surface. Starting it or the daemon alone does not create a conversation or delivery; pending situations wait for an already-running or host-scheduled agent to call the tools explicitly.
The host loads serve only in an interactive everyday conversation and serve-scheduled only in a separate manual or scheduled conversation. It never loads both profiles into one conversation. Profile isolation and agent lifecycle are host/operator responsibilities outside the plugin. Automated scheduling is supported only when the host provides a dedicated per-run MCP profile containing only serve-scheduled; otherwise fail closed by not scheduling it. Manual restricted use remains possible.
| Client | Integration model |
|---|---|
| Grok CLI 0.2.112 | Manual dedicated restricted profile only; merged config sources cannot prove immutable per-run isolation, so unattended scheduling is not advertised |
| Codex CLI | Local stdio; config layers are not claimed isolated by this plugin, so schedule only when the host/operator independently guarantees a dedicated per-run profile |
| Hermes Agent | Local stdio. Schedule only when the host guarantees a dedicated per-run profile |
| Claude Code Desktop | Local stdio; local tasks only when that version provides a dedicated per-task MCP profile |
The daemon may perform local sync, deterministic evaluation, queue maintenance, and the documented critical-only OS fallback. It never invokes an agent/LLM or sends prompts. Exact host responsibilities and command shapes are in docs/INTEGRATIONS.md.
The delivery contract
When an agent calls proactive_check:
- Read
warningsfirst. Stale-source warnings are not an all-clear. Areply_deadlineis a conservative candidate, not an action verdict. - Before speaking, confidently drop newsletters, marketing, automated receipts, FYI or FYI-CC with no ask, threads owned by someone else, and rows with no question, request, or decision for this user.
- Keep explicit reply, RSVP, or decision requests, user-owned deadlines, and unanswered questions directed to this user.
- Surface uncertain candidates, leave the whole lease unconfirmed, or snooze them from the interactive profile. Never silently discard uncertainty as non-actionable.
- After reviewing every row, only when choosing confirmation, use the
receipt_tokenfrom that check to callconfirm_deliveryexactly once for the entire reviewed lease. That confirmation includes candidates the host confidently and silently dropped. Never confirm a tokenless response. - Keep MCP tool names, descriptions, fields, and values in English. Speak to the user in the user's language.
- Keep interactive everyday and scheduled work in separate conversations. Load only
servein the former and onlyserve-scheduledin the latter, never both. The host/operator owns this isolation; if a dedicated per-run profile is unavailable, do not automate the scheduled run.
This confirmation step keeps delivery history accurate across crashes, retries, and multiple agents.
Tool surface
Memory
remember · recall · update · list_entities · forget
Situations and delivery
proactive_check · confirm_delivery · list_situations · get_situation · acknowledge_situation · snooze_situation · mute_situation · get_status
Release status
| Area | Now |
|---|---|
| Distribution | PyPI package proactive-mcp 0.2.0, installed with uvx |
| Google OAuth | Your own Desktop OAuth client (BYO) |
| Hosts | Grok CLI and Codex CLI for everyday use |
| Data | Local SQLite under ~/.proactive-mcp/ |
Scope and release decisions remain canonical in docs/PRODUCT_PLAN.md.
Documentation
| Guide | Purpose |
|---|---|
README.ko.md |
Korean README |
docs/SETUP_GOOGLE.md |
BYO Google OAuth (the public default) |
docs/INTEGRATIONS.md |
Onboarding and service commands, plus optional host recipes |
docs/STATE_MODEL.md |
Source, lease, collector, daemon, fallback, and receipt state semantics |
docs/MEMORY_MODEL_V2.md |
Memory model and tool contracts |
License
MIT © 2026 Kyungwoo Seo <hello@madrobot.net>
This project was built with OmO Native.
You can support this project on Ko-fi.
proactive MCP questions
How do I add proactive MCP to Claude Code?
Run claude mcp add proactive-mcp -- uvx proactive-mcp in your terminal. Add --scope user to make it available in every project.
How do I add proactive MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does this server use an LLM to detect events?
No, it uses a deterministic engine to evaluate rules against source data without running a host or LLM.
What level of access does the server have to my Google account?
Access is limited to read-only scopes for Gmail and Google Calendar.
Where is the data stored?
Memories, situations, and sync state are stored locally in a SQLite database.