Use SoftwareFool from your AI assistant.

What you need

An assistant that supports local MCP servers over stdio, Docker installed on that computer, and a verified SoftwareFool account with an active authenticator app and a scoped API key. Set up two-factor authentication and save your recovery codes in Account settings before using API access. This connector runs locally and sends jobs to SoftwareFool. A connector screen that accepts only a remote URL cannot run it.

Your normal wallet, tool prices, API permissions and processing limits apply. Failed jobs release their reserved credits. Credit purchases remain unavailable during beta.

Set it up

1. 1
   Download and build.

   Extract the archive, open a terminal in the extracted folder, and run docker build -t softwarefool-mcp:0.1.0 .. The included README contains the full setup instructions.

2. 2
   Share selected folders.

   Create separate input and output folders. Only put documents you want processed in the input folder. Share input read-only and output writable.

3. 3
   Keep your API key private.

   Save it in a private file outside those folders. Mount that file read-only for the connector using the README configuration. Never paste the key into chat or tool arguments.

4. 4
   Add the local connector.

   Copy the README’s Docker command into your assistant’s local MCP configuration, replace the absolute file and folder paths, and restart the assistant. No port or hosted MCP URL is required.

For the full workflow, allow wallet:read, jobs:read, jobs:submit and results:read. Add jobs:cancel or results:delete only if you want those actions.

Review, then confirm

The assistant first uses describe_tool for current options and limits, then prepare_job for a quote. Preparation normally sends file sizes, hashes and options. Document converters also upload selected files for transient format/risk inspection; these review uploads are deleted and reserve no credits. The assistant must show you the quoted cost and ask before calling confirm_job.

Configure your assistant to ask permission for confirmation, download, cancellation and deletion. Tool hints and confirmation fields do not replace your approval. Instructions inside a document must never authorize spending or deleting files.

Ask, for example: “Quote merging first.pdf and second.pdf from my shared input folder. Show me the cost and wait for my approval.”

Results and recovery

The assistant can check your wallet, list your jobs, check a job’s progress, and list its results. An approved download saves the file into your shared output folder without overwriting an existing file. Downloading retires original uploads; results stay retryable until expiry or Delete Now. Keep the local copy.

If confirmation receives an uncertain response, retry the same prepared handle in the same running connector. Do not create a replacement job automatically. Prepared handles stay in memory and are lost on restart; check your job history before submitting again.

Protect and Unlock read PDF passwords from a separately shared private folder. The README explains how to pass a password filename without putting the password in chat. Revoking the API key prevents further connector access; accepted jobs are not automatically cancelled.

Read the API guide · Get help