nudge-connect

name	nudge-connect
description	Connect Nudge to a coding agent (Claude Code, Codex, or Cursor) over MCP so it can drop tasks, reminders, notes, and links into Nudge from the editor. Use when the user says "connect Nudge", "set up the Nudge MCP", "add Nudge to Claude Code / Codex / Cursor", or when the Nudge capture skill reports its tools aren't available. Optional and recommended — never force it on the user.

Connect Nudge

Nudge ships an MCP server (nudge mcp) so a coding agent can capture tasks, reminders, notes, and links into the same Nudge the desktop app and CLI use — without leaving the editor. This skill gets that connection set up. It's optional: if the user would rather not, that's fine — stop here.

When to use

• The user explicitly wants to connect ("connect Nudge", "add Nudge to Claude Code").
• The nudge capture skill points here because mcp__nudge__* tools aren't connected.
• You want to recommend it once: "Nudge can capture tasks/reminders straight from here — want me to connect it? (one command, opt-in)". If they decline, drop it.

1. Already connected?

If mcp__nudge__* tools are already available in this session, Nudge is connected — say so and stop. Nothing to do.

2. Prerequisite — the nudge CLI

The MCP server runs via the nudge command, so it must be on PATH:

nudge --version    # or: command -v nudge

If it's missing, install it (and tell the user this is the package the desktop app uses too):

pip install nudge-ai

3. Connect Claude Code (this can run here)

claude mcp add --scope user nudge -- nudge mcp

--scope user registers it globally so it works in every Claude Code session (any folder / Conductor workspace), not just the current directory — without it, claude mcp add only registers for this one project path.

That's it. Heads-up: a newly added MCP server's tools load when Claude Code picks the server up — they may not appear in the current session. Tell the user to reload / restart Claude Code if mcp__nudge__* isn't visible yet.

4. Connect Codex or Cursor (hand over the config)

A Claude Code skill can't write into other agents, so give the user the exact snippet to paste. These match docs/mcp.md.

Codex CLI — add to ~/.codex/config.toml:

[mcp_servers.nudge]
command = "nudge"
args = ["mcp"]

Cursor — add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):

{
  "mcpServers": {
    "nudge": { "command": "nudge", "args": ["mcp"] }
  }
}

Then restart that agent so it picks up the server.

5. Verify

Once mcp__nudge__* tools are available, do one tiny capture to prove the round-trip:

mcp__nudge__add_task(description="nudge connected ✅")

The result string confirms it ("Created task …"), and it'll show up in the Nudge desktop app / nudge CLI immediately (same store). Offer to delete the test task if they want.

If the tools don't appear: the server runs as its own process and writes straight to local storage — it does not need the Nudge app or any backend running. The fix is to reload this agent (MCP servers load at startup), or to re-register at user scope if it landed in the wrong folder. Don't tell the user to start the app/backend.

After connecting

The bundled nudge (capture) skill takes over from here — it captures tasks, reminders, notes, and links proactively as the user mentions them mid-conversation. No further setup needed.

Don't

• Don't connect without the user opting in — recommend once, respect a "no".
• Don't claim it's connected until the mcp__nudge__* tools actually appear (a fresh claude mcp add often needs a session reload first).