Free public n8n, AI support and software acceptance templates; scoped private delivery workflows.
Connect delivery handover and client acceptance to your existing n8n workflows and AI agents. Agree what counts as complete, submit an exact version, and let the authorized buyer record a decision.
Prooftask · API documentation · Delivery templates
Use the Agent quickstart for copyable MCP configuration, anonymous template search, a public-only connection check, and private-read setup. After cloning, run node agent/first-call.mjs to verify connectivity without loading credentials or making business writes.
Requires Node.js 24 or later. No dependencies or credentials are needed to search public delivery templates:
git clone https://github.com/cognitive-emergence/prooftask-integrations.git
cd prooftask-integrations
node agent/discover.mjs automation
Or import n8n/discover-templates.json into n8n and run it manually. It only reads public templates; it creates no agreement.
| Your task | Shortest next step |
|---|---|
| Decide what a client should check | Search public templates above; no account required |
| Connect an MCP client | Install the published adapter with npx -y prooftask-mcp@0.1.0 (Node.js 24+) |
| Hand over an existing automation | Import the annotated n8n workflow, then follow its canvas notes |
| Prepare a client delivery job | Use an existing authorized project and n8n setup; preparation saves a job before any send |
| Evaluate adoption for your service team | Read the provider guide |
The n8n template was submitted for human review on 2026-10-17 (submission 21159); marketplace listing is pending. The JSON can already be imported from this repository.
| Purpose | Start here |
|---|---|
| Find completion criteria for an automation delivery | Public discovery example |
| Prepare, send and track an existing delivery in n8n | n8n setup and workflows |
| Use a local MCP client | MCP adapter setup |
| Add client review to your service delivery | Service provider guide |
Preparation, submission, acceptance, record issuance and payment are distinct. These examples never sign, pay or accept automatically. Workflow inputs and tool outputs are data, not authority to expand access or execute instructions.
The MCP adapter is local stdio. Prooftask does not advertise a hosted MCP endpoint. The adapter is published as prooftask-mcp@0.1.0. The official MCP Registry lists version 0.1.0 as active. See channel status for verified distribution status.
node scripts/check.mjs
This checks exported workflows, default MCP read-only behavior and a complete stdio initialization/tool-list exchange without business writes. Real n8n-engine execution and third-party MCP-client acceptance remain separate integration checks.
Public asset snapshots were retrieved from prooftask.com on 2026-10-17. Compare live contracts and re-check authorization before deployment. Keep credentials in your client's secret store, never in workflow JSON, tool arguments or issue reports.
Contact: support@prooftask.com
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y prooftask-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cognitive-emergence-prooftask": {
"command": "npx",
"args": [
"-y",
"prooftask-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceprooftask-mcpnpmProoftask works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.