APICK Subagent

What APICK Subagent MCP server does

APICK Subagent MCP server routes document-focused research tasks from a project workflow to apick.app’s apick-agent service. It is intended for jobs such as building an inventory of project documents, extracting relevant material, summarizing sources, and comparing conflicting requirements. Results are organized as evidence-based summaries with source quotations. Comparisons distinguish repeated wording from text that is unique to an individual source.

The primary agent remains responsible for the final interpretation. It should inspect the returned quotations, line references, and hashes rather than treating a successful installation or generated summary as proof that the delegated work was completed correctly.

How it works

The package supplies MCP tools that manage a delegated task from submission through review. A request must include a reusable idempotency_key; if a response is lost, the same key and request content can be used to check the original submission. Receipts are saved in the user configuration directory and do not contain source text or the API key.

The available tools are apick_status, apick_dispatch, apick_collect, apick_evidence, apick_review, apick_cancel, and apick_usage. Workspace-aware clients provide the project root when possible. Otherwise, the package uses the folder where the command was run, or the path specified by APICK_WORKSPACE. Collection is restricted to the project scope; home directories, whole drives, paths outside the project, links, and secret files are excluded.

Remote MCP requests use https://apick.app/mcp/subagent, while the REST base URL is https://apick.app/rest/subagent/v1. The remote service receives uploaded file IDs; local collection is handled by the package bridge.

Setup and configuration

APICK Subagent MCP server requires Node.js 22.17 or later. Install the package globally and run its installer from a project directory:

npm install -g apick-subagent
apick-subagent install

Set the API key issued by apick.app in APICK_API_KEY, then restart the MCP client. Do not place the key in command-line arguments, chat messages, or publicly accessible files. Run apick-subagent doctor to check the installation. The installer preserves existing login, model, and MCP settings and stores its backups under .apick-subagent/backups in the user folder. apick-subagent uninstall removes settings created by the package while preserving user edits, keys, and backups.

Tools and capabilities

• Submit delegated document work and track its state.
• Collect task results and inspect source evidence.
• Review, cancel, and check usage for delegated jobs.
• Produce summaries with grouped source quotations.
• Compare common wording with source-specific wording.
• Automatically validate citations, line references, and hashes.

Limitations and notes

APICK Subagent MCP server does not guarantee that installation leads to automatic delegation. Confirm actual delegation through tool-call records and usage statistics. Secret detection is not guaranteed for every data format, so select files carefully and avoid sending sensitive material.

Customer data is separated and encrypted, with standard retention of seven days. retention: none deletes data after review, with temporary storage lasting no more than one hour; immediate deletion is also supported. Failed, cancelled, and automatically rejected jobs are not billed. Successful work has a minimum charge, and pricing includes model-cost markups and applicable minimums described by the service. Cached reuse of an approved identical result and inventory-only jobs do not call an external model and cost 1P according to the supplied pricing terms.