Apify plugin for DeepSeek Harness
Search, run, and build Apify Actors directly from DeepSeek Harness.
What you get
| Component | Name | Purpose | Needs |
|---|
| Skill (entry point) | apify | Routes each Apify request to the right skill or tool. | - |
| MCP server | apify (https://mcp.apify.com/) | Searches Apify Store, fetches Actor details and docs. With a token it also runs Actors and reads their results. | APIFY_TOKEN to run Actors |
| Skill | apify-ultimate-scraper | Multi-step scraping workflows across 15+ platforms. | Apify CLI |
| Skill | apify-actor-development | Creates, tests, and deploys a new Actor. | Apify CLI |
| Skill | apify-actorization | Turns an existing project into an Actor. | Apify CLI |
| Skill | apify-generate-output-schema | Generates output schemas for an existing Actor from its source code. | - |
| Skill | apify-sdk-integration | Adds Actor runs to your own app with the apify-client package. | APIFY_TOKEN in your app |
Skills load when a request matches them, or run one directly as /<skill-name>. Skills marked "Apify CLI" need the Apify CLI installed and logged in.
Before you start
- Node.js
^22.19.0 || >=24.2.0. On older versions, dsh exits without printing anything.
- pnpm on PATH.
dsh plugin forwards to it.
- An Apify API token from Apify Console (free accounts work). Without a token only search/inspect tools load. If you already use the logged-in Apify CLI, the agent can run Actors through it instead (requires Full access sandbox mode).
Install
Plugins are installed per dsh profile. Use the profile you run:
dsh plugin --profile web add dsh-apify-plugin
Add your token to a .env file where you launch dsh:
# .env
APIFY_TOKEN=<your-apify-token>
Restart dsh. It reads the token once at startup, so a token set during a session has no effect.
Verify
Start a new session and ask:
List the Apify skills and the mcp__apify__ tools you can use.
You should see the six skills above. With a token, the tools include mcp__apify__call-actor. Without one, you get only search-actors, fetch-actor-details, search-apify-docs, and fetch-apify-docs.
Try it
Use Apify to find a good Actor for scraping Google Maps reviews. Show me its input schema and pricing. Don't run it.
Use Apify to scrape the top 10 Google search results for "web scraping best practices" and summarize what they have in common.
Configuration
Override either bundle row by id from your profile's cordis.patch.yml. See cordis.patch.yml in this repo for the full default. To change which tools load, edit the tools= query parameter in the MCP URL (docs, visual picker).
Troubleshooting
invalid_token on startup. Token is set but wrong. Fix it and restart.
The agent says it cannot run an Actor. You're in discovery-only mode. Set APIFY_TOKEN and restart.
npm reports root-owned files and suggests sudo chown. The default Workspace Write sandbox blocks writes outside your workspace, including the npm cache in ~/.npm, and npm reports that as an ownership problem. sudo chown doesn't help, so reject any prompt to run it. To get past the error, run the command that failed (such as apify create or npm install) yourself in the workspace directory and let the agent continue. Approving the agent's escalation or switching to Full access also works, but it gives the agent unrestricted access to your whole system, so do that only if you trust the model, or run dsh in a container or VM.
The plugin seems out of date or missing. Check that you installed it into the profile you're running. Each profile has its own copy.
Remove
dsh plugin --profile web remove dsh-apify-plugin
Note: Actor runs consume Apify usage on top of model provider costs.
Links
License
Apache-2.0. See LICENSE.
