Skip to main content

Qoder IDE integration

Copy for LLM

Qoder IDE is an agentic coding editor. It reads and edits your project, runs commands, and completes multi-step development tasks from a built-in chat.

The Apify plugin for Qoder connects the Qoder IDE to Apify's library of Actors and bundles:

  • The Apify MCP server for searching Apify Store, running Actors, and retrieving datasets through the Model Context Protocol (MCP).
  • An apify routing agent that picks the right tool or skill from a natural-language request.
  • Five built-in skills for common workflows (see Bundled skills below).
Help keep this page up to date

This integration uses a third-party service. If you find outdated content, please submit an issue on GitHub.

Prerequisites

Install the plugin

You can install the plugin two ways: a one-click install from the Qoder Marketplace, or a manual import of the downloaded plugin package. The one-click install requires Qoder IDE v1.23.0 or newer.

One-click install

  1. Open the Apify plugin on the Qoder Marketplace and select Qoder IDE to install directly.

    Apify plugin page on the Qoder Marketplace with the Qoder IDE install option

  2. The Qoder IDE opens an install dialog. Review the plugin details and select Install Plugin.

  3. The Apify plugin appears under Installed. Make sure it's enabled.

Manual install

If you're on an older version or prefer to install from a file:

  1. On the Apify plugin on the Qoder Marketplace, under For Human, select the download icon to download the plugin package.

  2. In the Qoder IDE, open the account menu and select Qoder Settings.

  3. Select Plugins, then under Custom select Import and choose the plugin package you downloaded.

  4. The Apify Qoder Plugin appears under Custom. Make sure it's enabled.

After installing with either method, select MCP Server to confirm the apify server is registered from the plugin. It connects to https://mcp.apify.com and exposes the Apify tools.

Authenticate to Apify

Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data.

On the first action that needs your account, the Qoder IDE opens a browser tab for the Apify OAuth flow. Review the permissions and allow access to finish signing in. The connection stays authenticated for future sessions, and you can revoke access at any time in Apify Console > Settings > Integrations.

Run your first prompt

Open the chat and describe what you want in natural language. The apify agent routes the request to the right tool or skill, so you don't need to name tools yourself.

What Apify tools do you have available?

The agent lists the Apify MCP tools and skills it can call.

Qoder IDE chat listing the available Apify tools and skills

Bundled skills

SkillDescription
apify-ultimate-scraperExtraction using existing Actors for multi-step scraping and lead-generation workflows.
apify-actor-developmentFull Actor lifecycle - template selection, development, local testing, and deployment with apify push.
apify-actorizationConverts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors.
apify-generate-output-schemaGenerates dataset and key-value store schemas for existing Actors.
apify-sdk-integrationIntegrates Actor execution into applications using the apify-client package.

Troubleshooting

The Apify server doesn't appear under MCP Server

Confirm the Apify plugin is enabled on the Plugins page, then open the MCP Server page again. If the server is still missing, restart the Qoder IDE so the plugin's MCP server registers.

Actor runs time out

Increase the request timeout for the apify server on the MCP Server page.

Browser doesn't open, or OAuth fails

If the browser doesn't open automatically, copy the OAuth URL shown by the IDE and paste it into your browser manually. If sign-in still fails, authenticate with an API token from Apify Console > Settings > Integrations.

Limitations

  • Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts.
  • Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See Billing for details.
  • Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing.

Resources