This npm package is the installer and thin launcher wrapper for PatchX Freenote Agent. It downloads or verifies the matching native patchxnote CLI binary from GitHub Releases, verifies checksums.txt, and installs it into a user-writable directory before delegating runtime commands to that binary.

PatchX Freenote Agent is the local AI assistant connector for PatchX Freenote. It lets an MCP-capable AI assistant find PatchX Freenote records, inspect AI-generated results, create Markdown drafts, and manually send user-approved messages to Feishu, DingTalk, or another webhook.

Version 0.2.15 defaults to the production API at https://freenote.patch-x.cn. When upgrading from test, update or remove explicit server-address overrides in your CLI and MCP host configuration, then run mcp login in the same runtime and profile that launches MCP. Test credentials and records do not migrate to production.

Production service: https://freenote.patch-x.cn/ · MCP setup · Download App

Give this one-line prompt to an AI assistant:

Help me connect PatchX Freenote MCP and install the PatchX Freenote MCP Skill when the client supports Agent Skills. Use the production service at https://freenote.patch-x.cn/ and the setup page at https://freenote.patch-x.cn/mcp/setup/; if existing configuration explicitly points to the old test service, update the server address used for this connection to production first. First, if this is a local command-capable environment, run npx -y patchxnote-agent@latest skill install on this machine so future or long sessions remember the PatchX Freenote SOP; if the current client does not support Skill installation, do not treat that as a connection blocker and continue with MCP setup according to the client's capabilities. Identify the MCP client you are running in: if this is a local MCP client such as Codex, Cursor, VS Code, Claude Desktop, Claude Code, or Windsurf, run npx -y patchxnote-agent@latest setup --client <client-id> on this machine in the same OS/runtime that will later launch the MCP server. If this is an AI client or cloud platform that cannot run local commands but supports Remote MCP, custom connectors, custom MCP services, or tool plugins, create a custom MCP connector named PatchX Freenote MCP and connect it with this PatchX Freenote Remote MCP URL: https://freenote.patch-x.cn/mcp. If you are not sure which client ID or config format to use, local clients should first run npx -y patchxnote-agent@latest mcp config and use the printed generic stdio config, while remote clients should look for a Remote MCP Server URL, MCP Server URL, or Custom Connector setup entry. For login, open the browser and let me complete PatchX Freenote phone-code authorization there; do not ask me to paste OTP codes, OAuth codes, authorization codes, access tokens, refresh tokens, or webhook secrets into chat. After setup, call patchxnote_get_current_user and patchxnote_list_memories with {"platform":"mobile","limit":5} to verify it works. References: https://github.com/ZsTs119/patchx-freenote-agent and https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd

The npm package includes an Agent Skills package at skills/patchxnote-mcp/. Compatible agents can install or refresh it with:

npx -y patchxnote-agent@latest skill install

The skill teaches the AI the PatchX Freenote SOP. MCP setup and browser login still use the commands below. By default, the installer writes under the user's home directory at .agents/skills/patchxnote-mcp; use --agent <id> only after that client's local skills directory is verified.

Useful skill installer options are --dry-run --json, --home <path> or PATCHXNOTE_AGENT_SKILL_HOME=<path>, --agent universal|codex|cursor|claude-code|gemini-cli|github-copilot|all, and --force. Existing unmanaged or manually edited patchxnote-mcp folders are protected unless --force is supplied.

Run setup for a supported local client:

npx -y patchxnote-agent@latest setup --client cursor
npx -y patchxnote-agent@latest setup --client vscode
npx -y patchxnote-agent@latest setup --client codex

PatchX Freenote Agent currently exposes two login surfaces and two MCP service shapes:

Mode	Entry	Use when
Browser MCP login	`npx -y patchxnote-agent@latest mcp login`	Recommended for desktop editors and local MCP hosts.
Terminal CLI login	`npx -y patchxnote-agent@latest login`	Terminal-only users, headless runtimes, or the legacy local Agent path.
Local MCP service	`npx -y patchxnote-agent@latest mcp serve`	VS Code, Cursor, Codex, Claude Desktop, Windsurf, Trae, Qoder, WorkBuddy, and other stdio MCP clients.
Hosted remote MCP gateway	`https://freenote.patch-x.cn/mcp`	Feishu Aily, Doubao Work Partner, Tencent Agent Development Platform, enterprise WorkBuddy, and other platform clients that cannot run local commands.

npx -y patchxnote-agent@latest mcp login
npx -y patchxnote-agent@latest mcp status
npx -y patchxnote-agent@latest mcp logout --local-only

Print the generic MCP config manually:

npx -y patchxnote-agent@latest mcp config

The generated config uses this universal local stdio MCP command:

npx -y patchxnote-agent@latest mcp serve

The older terminal Agent login remains available for legacy local CLI/MCP fallback:

npx -y patchxnote-agent@latest login

setup reuses the same mcp login browser OAuth flow. The GoServer website owns phone OTP input; the local Agent owns the loopback callback, token exchange, secure storage, and stdio bridge. mcp serve never opens a browser during editor startup. It stores credentials in the OS-native keychain and keeps MCP config free of phone numbers, OTP codes, access tokens, refresh tokens, webhook secrets, and base URL by default.

P0 local client IDs: vscode, cursor, codex, claude-code, claude-desktop, windsurf, trae, qoder, workbuddy.

Platform clients such as Feishu Aily, Doubao Work Partner, Tencent Agent Development Platform, and enterprise WorkBuddy need the hosted remote MCP gateway plus platform-console acceptance; local npx setup is for desktop and terminal clients.

If a client rejects npx or times out during first binary download, run the stable absolute-path fallback:

npx -y patchxnote-agent@latest install --print-config

It currently exposes 19 MCP tools grouped around account/record lookup, webhook configuration and sending, and explicit AI result inspection.

Common npm wrapper commands:

npx -y patchxnote-agent@latest skill install
npx -y patchxnote-agent@latest setup --client cursor
npx -y patchxnote-agent@latest mcp login
npx -y patchxnote-agent@latest mcp status
npx -y patchxnote-agent@latest mcp config
npx -y patchxnote-agent@latest mcp serve
npx -y patchxnote-agent@latest install --print-config

Common CLI examples:

patchxnote model-io list --platform mobile
patchxnote model-io packaged-result --request-id <request_id> --platform mobile --out ./packaged-result.json
patchxnote model-io provider-response --request-id <request_id> --platform mobile --out ./provider-response.json
patchxnote webhook set "Product Feishu" --type feishu --url-stdin
patchxnote webhook send --target "Product Feishu" --file ./message.md

Webhook aliases can contain Chinese text, spaces, and dots.

Server-backed PatchX Freenote data access remains read-only through dedicated /v1/agent/** APIs. Record lookup can include formal saved results and readable model-generated outputs returned by the server. Local webhook tools can configure named targets and perform explicit manual sends. AI result tools can inspect source text, AI response, parsed result, and final result when explicitly called. MCP config contains no phone number, OTP, access token, refresh token, webhook secret, or base URL by default. The CLI stores credentials and webhook secrets in the OS-native keychain when available, never lists webhook URLs or signing secrets back, and does not expose raw audio, audio downloads, hardware write actions, payment flows, or Admin APIs.

For full installation, MCP setup, security notes, and troubleshooting, read the GitHub documentation: