PatchX Freenote Agent

io.github.ZsTs119由 GitHub 帳號 ZsTs119 發布v0.2.15更新於 Oct 24, 2026

PatchX Freenote MCP: summaries, memories, model results and user-approved webhook workflows.

概覽

AI 產生的概覽

把 PatchX Freenote 帳號接入助理,用來尋找已同步的紀錄、檢視已儲存的 AI 結果、產生 Markdown 草稿並送出經確認的 webhook。

可以做什麼
  • 檢視帳號狀態、配額、模型用量與已綁定的錄音卡
  • 依 mobile 或 desktop 平台列出、搜尋並讀取已同步紀錄
  • 檢視 AI 處理紀錄及其來源文字、模型回應、解析結果與最終結果,並可匯出到本機檔案
  • 管理本機 webhook 別名與範本,把紀錄轉成 Markdown、儲存草稿並送出經確認的訊息
  • 安裝隨套件提供的 Agent Skill,為相容的助理補充安裝與使用說明
適用情境
當你的筆記或錄音已同步到 PatchX Freenote,並希望助理幫你查找這些紀錄、檢視為其儲存的 AI 結果,或把某筆紀錄整理成經審閱的 Markdown 訊息送到飛書等團隊 webhook 時適用。
執行需求
本機 npm 啟動器需要 Windows、macOS 或 Linux(amd64 或 arm64)上的 Node.js 18+;也可使用支援 Remote MCP 與 OAuth 的平台連接託管端點。需要一個已同步紀錄的 PatchX Freenote 帳號,並透過安裝指令在瀏覽器登入。安裝須在之後啟動伺服器的同一作業系統/執行環境中進行,且需有可用的系統憑證儲存。
安裝前請注意
紀錄來源文字、AI 結果、匯出檔案與 webhook 目標可能屬於敏感資訊,請只在可信任的本機 MCP 宿主中使用,並在分享前審閱內容。webhook 網址與簽章密鑰保存在本機憑證儲存中,不要貼到聊天或留在指令歷史裡。送出需明確手動觸發,但確實會向所設定的 webhook 發出外部網路請求。安裝會寫入用戶端設定檔,只有在明確使用強制參數時才會覆蓋既有的 skill 資料夾。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 PatchX Freenote Agent,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

PatchX Freenote Agent

PatchX Freenote was formerly called PatchXNote. Existing patchxnote-agent commands, patchxnote-mcp Skill installs, MCP configuration and credentials remain compatible.

English | 简体中文

[npm version] [GitHub release] [MCP Registry] [skills.sh]

Connect your synced PatchX Freenote records to AI assistants. Find records, review existing AI results, create Markdown drafts, and share approved content through webhooks.

Production service · MCP setup · Download App · User guide (Chinese)

[Connect your PatchX Freenote records to AI assistants]

Quickstart · Connection options · Skill · Usage examples · Troubleshooting · Reference

Published Channels

ChannelPublic entryWhat is available
npmpatchxnote-agentVersioned CLI installer/launcher and bundled Skill; current release 0.2.15.
GitHub Releasev0.2.15Six Windows/macOS/Linux binaries, checksums, and artifact attestations.
MCP official RegistrySearch the retained ID · Version recordRegistered as io.github.ZsTs119/patchxnote-agent.
Vercel skills.shpatchxnote-mcpNew repository source, searchable as PatchX Freenote; Skill ID remains patchxnote-mcp.

These links show publication and directory listing. The 0.2.15 verification record documents artifact checks, Windows installation, local protocol discovery, and Registry readback; client/platform acceptance is tracked separately.

Choose Your Connection

Your environmentUseRequirements
Desktop editor or local MCP hostnpx -y patchxnote-agent@latest setup --client <client-id>Node.js 18+, Windows/macOS/Linux on amd64 or arm64, and a PatchX Freenote account.
Platform that supports Remote MCP and OAuthhttps://freenote.patch-x.cn/mcpConfigure a custom connector and complete that platform's authorization flow; no local Node.js installation is required for this route.
Assistant that supports Agent SkillsInstall PatchX Freenote MCP SkillAdds setup and usage instructions; complements the MCP connection.

Records must already be synced to PatchX Freenote and available to your account. Recorder-card connection, audio processing, and recording remain in the App/PC clients. Read records from the platform you select: mobile or desktop.

Quickstart

[Choose a client, authorize in the browser, and verify the connection]

1. Set up your local client

If your assistant supports Agent Skills, install the Skill first. MCP setup also works without it. Choose one command for the client you use:

ClientCommand
Cursornpx -y patchxnote-agent@latest setup --client cursor
VS Codenpx -y patchxnote-agent@latest setup --client vscode
Codexnpx -y patchxnote-agent@latest setup --client codex
WorkBuddy desktopnpx -y patchxnote-agent@latest setup --client workbuddy

Setup checks browser OAuth login and writes or prints the appropriate MCP config. Run it in the same OS/runtime that will launch MCP: Windows desktop apps and WSL/remote sessions use different credential stores. See Client Setup for other clients and manual configuration.

2. Authorize in the browser

Complete the PatchX Freenote sign-in page opened by setup. Keep phone verification codes and credentials on that page. If you need to start browser login explicitly:

sh
npx -y patchxnote-agent@latest mcp login

3. Verify and use

sh
npx -y patchxnote-agent@latest mcp status --verify --output json

Refresh or restart your MCP client, let it discover the available tools, then ask: “Find up to five of today's mobile records.” A successful empty result is normal when that account/platform has no matching records. See Verify the Install for additional checks.

Using a hosted platform instead

Create a custom MCP connector named PatchX Freenote MCP, set its server URL to https://freenote.patch-x.cn/mcp, complete the platform's OAuth flow, and refresh its tool list. Follow the platform-specific instructions in client integration notes; support and acceptance vary by platform.

Copy the complete prompt for an AI assistant
text
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

Common Workflows

GoalAsk your assistant
Find synced records“Find today's mobile records.”
Inspect an existing AI result“Show the source text and saved AI result for this record.”
Prepare content to share“Create a Markdown draft from this record. Let me review it before sending.”
Use a local webhook“Send this approved Markdown to my Product Feishu webhook.”

An existing record/result is the input. Local draft files and local webhook aliases require the local tools that provide those capabilities; check the connected endpoint's tool list before using them.

PatchX Freenote MCP Skill

The Skill gives compatible assistants reusable setup, authorization, record lookup, result inspection, and approved webhook instructions. The npm package bundles it, so the recommended install does not require a separate GitHub clone:

sh
npx -y patchxnote-agent@latest skill install

This installs the Skill into the user's .agents/skills/patchxnote-mcp directory by default. It does not log in to PatchX Freenote or start an MCP server.

Skill install options and existing-folder handling

Useful skill installer options:

OptionUse
--dry-run --jsonPreview target paths and conflict status without writing files.
--home <path> or PATCHXNOTE_AGENT_SKILL_HOME=<path>Install into a test or alternate home directory.
--agent universal|codex|cursor|claude-code|gemini-cli|github-copilot|allTarget a known local skill directory family after its location is verified.
--forceReplace an existing unmanaged or manually edited patchxnote-mcp skill after explicit user intent.

The installer is idempotent. If an existing patchxnote-mcp directory differs and is not managed by this package, it refuses to overwrite it unless --force is supplied. Managed installs include .patchxnote-agent-skill.json with the package version and source hash.

Alternative: install with the skills CLI

For users of the standard skills CLI, this Codex example installs from GitHub into the current project. It installs the Skill, not the MCP connection. Choose either this route or the npm-bundled install above.

sh
npx -y skills add ZsTs119/patchx-freenote-agent --skill patchxnote-mcp --agent codex --yes

Login And MCP Modes

The client transport and the source of its tools are separate:

  • mcp serve speaks stdio to the local client. In default auto mode, matching, unexpired browser OAuth credentials select a proxy to the hosted MCP service; otherwise it uses the local implementation.
  • The local implementation provides 19 tool definitions in 0.2.15. Their data calls still require appropriate authentication. A proxied or directly connected hosted service supplies its own tool set and may differ.
  • Use the connected endpoint's tools/list result as the source of truth for available tools. Local filesystem and webhook capabilities listed below describe the local implementation.
  • mcp login is the browser OAuth entry. Terminal-only patchxnote login remains the separate legacy Agent login. mcp serve does not open a login browser when the editor starts.

Client Setup

Supported clients and advanced setup flags

Local setup supports these client IDs:

text
vscode, cursor, codex, claude-code, claude-desktop, windsurf, trae, qoder, workbuddy

vscode, cursor, codex, claude-desktop, and windsurf can write a local config file after confirmation. claude-code, trae, qoder, and workbuddy return manual commands or copyable config in V1. Platform clients such as Feishu Aily, Doubao Work Partner, Tencent Agent Development Platform, and enterprise WorkBuddy require the hosted remote MCP gateway and platform-console acceptance instead of local npx.

Useful setup flags:

sh
patchxnote setup --client cursor --dry-run --print-configpatchxnote setup --client cursor --yespatchxnote setup --client cursor --no-browserpatchxnote setup --all-local-supported --dry-runpatchxnote setup --client cursor --output json

Run setup in the same OS/runtime that will later launch MCP. For example, a Windows desktop editor needs Windows Credential Manager credentials, while a WSL or remote VS Code session needs credentials in that Linux runtime.

MCP Configuration

Manual stdio configuration and absolute-path fallback

For generic local stdio MCP hosts, use the pure JSON printed by:

sh
npx -y patchxnote-agent@latest mcp config

The default config looks like this:

json
{  "mcpServers": {    "patchxnote": {      "command": "npx",      "args": ["-y", "patchxnote-agent@latest", "mcp", "serve"]    }  }}

Some clients may require a wrapper-specific field such as type: "stdio" or a different top-level key, but the command and args stay the same. If a client rejects npx, kills slow cold starts, or requires allowlisted absolute paths, use the fallback printed by:

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

The fallback config uses the installed binary path:

json
{  "mcpServers": {    "patchxnote": {      "command": "/absolute/path/to/patchxnote",      "args": ["mcp", "serve"]    }  }}

MCP Tools

Local implementation: 19 tool definitions

Account And Record Lookup

ToolPurpose
patchxnote_get_current_userShow the current PatchX Freenote account status.
patchxnote_list_recorder_cardsList bound recorder cards with masked identifiers only.
patchxnote_get_quota_summaryShow current quota.
patchxnote_get_model_usage_summaryShow current-month AI usage and charged quota.
patchxnote_list_memoriesList records for mobile or desktop.
patchxnote_search_memoriesSearch record basics cached in the current MCP session.
patchxnote_get_memoryShow safe basic information for one record.

Webhook Configuration And Sending

ToolPurpose
patchxnote_list_webhook_targetsList local webhook aliases and masked metadata.
patchxnote_configure_webhook_targetCreate or update a webhook alias; URL and secret inputs are write-only.
patchxnote_remove_webhook_targetRemove a webhook alias and best-effort clean up stored secrets.
patchxnote_list_webhook_templatesList built-in Markdown templates.
patchxnote_render_webhook_messageRender a record into Markdown and optionally save a local draft.
patchxnote_export_model_ioExport a complete AI processing record to a user-chosen local file.
patchxnote_send_webhookManually send Markdown, a draft, a rendered record, or a test message to target aliases.

AI Result Inspection

ToolPurpose
patchxnote_list_model_io_tracesFind AI processing runs and the follow-up request_id.
patchxnote_get_model_io_source_textInspect or export the source text used for that run.
patchxnote_get_model_io_provider_responseInspect or export the AI response.
patchxnote_get_model_io_parsed_resultInspect or export the parsed AI result.
patchxnote_get_model_io_packaged_resultInspect or export the final result.

Record tools require an explicit platform argument: mobile or desktop. The record list now includes formal saved results plus readable model-generated outputs when the server has model IO data. patchxnote model-io list remains the lower-level AI processing list for finding request IDs and filtering by task or state.

Webhook MCP tools share the same local config, keychain, templates, and sender modules as the CLI. They do not return full webhook URLs or signing secrets, and send calls perform external network requests only when the MCP client explicitly invokes the send tool.

AI result tools are explicit inspection tools. They may expose source text or AI payloads for the logged-in user, so use them only from trusted local MCP hosts. Large fields should be written to an explicit local out file.

CLI Commands

CLI command reference

The examples below are independent commands. Choose the operation for your task; they are not one script to run from top to bottom.

Browser MCP login and local MCP service:

sh
patchxnote versionpatchxnote mcp loginpatchxnote mcp statuspatchxnote mcp configpatchxnote setup --client cursorpatchxnote mcp serve

Terminal CLI login:

sh
patchxnote loginpatchxnote auth status

List AI processing runs and export results:

sh
patchxnote model-io list --platform mobilepatchxnote model-io source-text --request-id <request_id> --platform mobile --out ./source.txtpatchxnote model-io provider-response --request-id <request_id> --platform mobile --out ./provider-response.jsonpatchxnote model-io parsed-result --request-id <request_id> --platform mobile --out ./parsed-result.jsonpatchxnote model-io packaged-result --request-id <request_id> --platform mobile --out ./packaged-result.jsonpatchxnote model-io export --request-id <request_id> --platform mobile --out ./model-io.json

Get request_id from patchxnote model-io list --platform mobile|desktop when you need a lower-level AI processing run. MCP patchxnote_list_memories returns id and platform for record rendering, drafts, webhook workflows, and model IO field tools; for model-generated entries, that id can be the same value as request_id.

Configure and send webhooks:

sh
patchxnote webhook set "Product Feishu" --type feishu --url-stdinpatchxnote webhook listpatchxnote webhook test "Product Feishu"patchxnote webhook draft --memory-id <memory_id> --platform mobile --out ./patchxnote-drafts/examplepatchxnote webhook send --target "Product Feishu" --file ./message.mdpatchxnote webhook send --target "Product Feishu" --draft ./patchxnote-drafts/examplepatchxnote webhook remove "Product Feishu"

Useful global flags:

sh
--server-base-url <url>   PatchX Freenote API base URL--profile <name>          local profile name--output json             machine-readable output where supported--config <path>           non-secret config file path

The npm package is a small installer/launcher wrapper:

sh
npx -y patchxnote-agent@latest mcp loginnpx -y patchxnote-agent@latest mcp statusnpx -y patchxnote-agent@latest mcp confignpx -y patchxnote-agent@latest mcp servenpx -y patchxnote-agent@latest skill installnpx -y patchxnote-agent@latest loginnpx -y patchxnote-agent@latest setup --client cursornpx -y patchxnote-agent@latest installnpx -y patchxnote-agent@latest update

Webhook URLs and optional Feishu/DingTalk signing secrets are stored in the local secure credential store, not in the non-secret config file. --url-stdin and --secret-stdin avoid shell history. CLI and MCP webhook sending is manual only, does not follow redirects, and surfaces provider errors directly.

patchxnote model-io export is the preferred complete AI processing export command. patchxnote webhook export-model-io remains available for compatibility.

Verify The Install

These checks do not sign you out or overwrite client configuration:

sh
npm view patchxnote-agent@latest version --registry https://registry.npmjs.orgnpx -y --registry https://registry.npmjs.org patchxnote-agent@latest skill install --dry-run --jsonnpx -y --registry https://registry.npmjs.org patchxnote-agent@latest mcp confignpx -y --registry https://registry.npmjs.org patchxnote-agent@latest mcp status --output json

After authorization, add --verify to mcp status to verify access. If the native binary is on PATH, patchxnote version reports its version and release commit. The current published release is 0.2.15.

Troubleshooting

ProblemWhat to check
patchxnote is not found after installAdd the printed install directory to PATH, then open a new terminal.
Login says credential storage is unavailableCheck that macOS Keychain, Windows Credential Manager, or Linux Secret Service is available and unlocked. For local development only, set PATCHXNOTE_AUTH_INSECURE_FILE_KEYCHAIN=true.
MCP login expired or points at the wrong serverRun npx -y patchxnote-agent@latest mcp logout --local-only, then run npx -y patchxnote-agent@latest mcp login again in the same runtime.
MCP host cannot start the serverIf first start is slow or the client rejects npx, run npx -y patchxnote-agent@latest install --print-config once and use the printed absolute command path.
Setup writes credentials in the wrong placeRun setup from the same OS/runtime that will launch MCP. Windows desktop apps, WSL terminals, and VS Code Remote do not automatically share keychain credentials.
Need to undo setupRestore the timestamped .bak-YYYYMMDDTHHMMSSZ file printed by setup, or remove only the patchxnote MCP server entry from the client config.
Record list is emptyCheck that you selected the correct platform: mobile or desktop; use model-io list for lower-level AI processing runs.
Webhook did not sendConfirm the alias exists, the target is enabled, and check the provider error returned by the command.
Checksum verification failsRetry later or pin a known version; the installer refuses unchecked binaries.
skill install says the target already exists and differsThe target contains an unmanaged or manually edited patchxnote-mcp skill. Inspect or back it up first; rerun with --force only when you want PatchX Freenote Agent to replace that skill folder.
Wrong server environmentUse --server-base-url <url> when logging in to another environment, and use a separate profile.
New release returns ETARGETCheck npm config get registry. A mirror may not have synced yet; use the one-command official-registry example below.
sh
npx -y --registry https://registry.npmjs.org patchxnote-agent@latest install --print-config

This applies the registry choice to this command only. If a GitHub download is slow, retry later; the npm-bundled Skill avoids a separate repository clone.

Existing test-environment configuration

Version 0.2.12 and later default to production. Existing explicit --server-base-url flags, PATCHXNOTE_SERVER_BASE_URL / legacy PATCHNOTE_SERVER_BASE_URL environment variables, and server.base_url config values override that default; update or remove test-server overrides in both the terminal and MCP host configuration.

Run mcp login in the same OS/runtime and profile that starts MCP, then check mcp status --verify. OAuth credentials are bound to the server address, so test login does not authenticate production. This update does not migrate test accounts or records. To keep both environments, use separate profiles and an explicit base URL for each.

Sign Out And Undo Setup

Choose the action you need; these are separate maintenance operations:

ActionCommand or instructions
Sign out of MCPnpx -y patchxnote-agent@latest mcp logout
Remove only local MCP credentialsnpx -y patchxnote-agent@latest mcp logout --local-only
Undo client setupRestore the timestamped backup printed by setup, or remove its patchxnote entry from that client's configuration.
Uninstall the managed native binarynpx -y patchxnote-agent@latest uninstall

Security And Risk Notice

  • PatchX Freenote server data access is read-only. Agent does not bind hardware, read raw audio, trigger model runs, handle payments, or expose Admin APIs.
  • Local webhook configuration and user-approved sending are supported local actions. Sending is explicit, with no automatic background delivery.
  • Credentials use OS-native secure storage; MCP config contains no bearer tokens or webhook secrets. Windows, WSL, and remote runtimes do not automatically share credentials.
  • Records are scoped to the authenticated account and selected mobile or desktop platform. Source text, AI results, exported files, and webhook destinations may be sensitive.
  • Review content before sharing and use trusted MCP clients. Report vulnerabilities through SECURITY.md, without posting credentials or private records in public issues.

Current Limitations

Search covers record basics cached during the current local MCP session. Linux headless environments need an available secure credential store. Hosted-platform acceptance and local installation are separate; see the client status notes. This is a public beta, without a production SLA.

Release History

GitHub Releases

Release highlights from 0.2.6 to 0.2.15

0.2.15 Highlights

  • Corrects the MCP Registry namespace to preserve GitHub owner casing: io.github.ZsTs119/patchxnote-agent.
  • Adds the mcp serve launch arguments and validates release metadata before publication.
  • Keeps the existing runtime behavior and Skill license.

0.2.13 Highlights

  • Unifies the English and Chinese setup prompts across README, npm, the bundled Skill, and marketplace copy.
  • Explicitly names the production service, Remote MCP endpoint, setup page, and App download URL; existing test-address overrides must be updated when switching.
  • Points npm and plugin homepage metadata to the production setup page and retires obsolete domain proposals in current guidance.

0.2.12 Highlights

  • Defaults to the production API at https://freenote.patch-x.cn; hosted MCP uses https://freenote.patch-x.cn/mcp.
  • Keeps explicit server flags, environment variables, and config-file overrides available for test environments.
  • Documents production re-login and migration of existing test-server configurations.

0.2.11 Highlights

  • Bundles the canonical PatchX Freenote MCP Skill inside the npm package.
  • Adds npx -y patchxnote-agent@latest skill install for npm-based skill installation without relying on a separate skills CLI or GitHub clone.
  • Makes skill installation idempotent, records a managed marker, and protects manually edited skill folders unless --force is explicitly used.
  • Extends skill package sync and validation so OpenAI, Claude, and npm copies stay byte-identical to skills/patchxnote-mcp/.
  • Updates the one-line setup prompt and discovery metadata to prefer the npm-bundled skill installer while preserving MCP setup, browser OAuth, and tool verification.

0.2.10 Highlights

  • Adds the reusable PatchX Freenote MCP Skill at skills/patchxnote-mcp/ so compatible AI clients can keep the setup and usage SOP across fresh or long sessions.
  • Adds OpenAI/Codex, Claude Code, Agent Skills, MCP Registry, Smithery, and third-party directory draft packaging and listing materials.
  • Adds MCP Registry metadata through server.json and package.json#mcpName, plus local validation and stdio smoke scripts for release evidence.
  • Updates the one-line setup prompt so agents install the skill when supported, then run MCP setup, browser OAuth, and tool verification without asking users to paste codes or tokens into chat.

0.2.9 Highlights

  • Polishes the browser OAuth loopback success and failure pages shown after patchxnote mcp login.
  • Keeps the post-login result page focused on plain user guidance, without exposing OAuth codes, state values, or token-shaped details.
  • Adds regression coverage for the browser callback pages so future changes keep those sensitive details out of the UI.

0.2.8 Highlights

  • Adds patchxnote setup --client <id> and npm wrapper delegation with dry-run, JSON output, confirmation, config printing, force repair, and local MCP smoke hooks.
  • Adds a client registry for VS Code, Cursor, Codex, Claude Code, Claude Desktop, Windsurf, Trae, Qoder, WorkBuddy, Feishu/Doubao, Tencent platform, and P1 follow-up clients.
  • Adds JSON and TOML config merge adapters with backup, conflict detection, rollback, and manual JSONC mode.
  • Adds patchxnote mcp login/status/logout, browser OAuth with PKCE, MCP OAuth secure storage, and remote /mcp stdio proxy mode with local fallback.
  • Adds website page specs, detail-page copy, and remote platform gateway design for product-style onboarding.

0.2.6 Highlights

  • MCP expands to 19 tools across account/record lookup, webhook delivery, and AI result inspection.
  • Webhook workflows are available to MCP: configure named aliases and manually send to Feishu, DingTalk, or generic webhooks.
  • AI processing runs can be listed first, then inspected by request_id for source text, AI response, parsed result, and final result.
  • Record lists can now include readable model-generated outputs returned by the server, so users can find a record first and then inspect its source text, AI response, parsed result, or final result.
  • Webhook aliases containing dots, Chinese text, or spaces now persist and reload correctly from the local config file.
  • README, npm README, and public visual assets have been refreshed for the new user-facing positioning.

Development

For architecture, local development, and checks appropriate to your change, read AGENTS.md, engineering rules, and the release and maintenance runbook. Metadata-only releases use the affected-module validation described in that runbook.

Release Notes For Operators

The runbook covers version synchronization, GitHub Release assets, npm Trusted Publishing, and release verification. Current evidence: 0.2.15.

License

This repository is currently published without an open-source license. Contact PatchX Freenote before redistributing or embedding it in another product.

來源:README.md,提交 7a4f52c

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.2.15最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。