Skip to main content
Extensions

Connectors

Connect Qoder to external services through marketplace integrations or custom MCP servers.

Connectors let Qoder use tools provided by an external service. Use one when a task needs information or actions outside the current workspace, such as project management, databases, documentation, or automation services.

Install a Connector

  1. Select Extensions in the left sidebar.
  2. Open the Connectors tab.
  3. Browse by category, switch between Popular and Newest, or use Search.
  4. Open View details and review the service, publisher, capabilities, and requested access.
  5. Select Install, then complete any authentication or setup requested by the service.

Browse recommendations and Partner badges

To discover featured connectors, browse New & noteworthy and select its heading for the full list. This section appears only when the marketplace is accessible and recommendations are available. Otherwise, use categories, sorting, or search. A Partner badge identifies an offering from a partner. Before installing, open its details and review the publisher, purpose, required permissions, and external dependencies for your task. Visible content also depends on account or organization restrictions. Recommended connectors still require the service’s sign-in, authorization, or connection setup after installation. Recommendations do not apply to manually added custom MCP servers. After installation, begin with a read-only request. Confirm that the returned account and data scope are correct before asking Qoder to create, update, or delete external data.

Use connectors with an interface

Qoder can display interactive interfaces supplied by connectors or plugins that support MCP Apps. To build a custom interface and keep it open in Qoder, see the UI plugin guidance in Plugins. Install and enable the extension, complete account authorization, and confirm that its tools have loaded. An app appears only when the extension provides app resources and an entry point; ordinary MCP connectors may have no interface. Open an available app entry or inspect an interactive result after a tool call. Depending on what the app declares, it can appear inline in the conversation or in a separate work surface. Inline-only apps cannot be forced into a separate page. Use the app's associated conversation for follow-up requests and state the intended task clearly. When downloading a file offered by an app, check the filename and destination in the save dialog before confirming. Writes or submissions in an app remain subject to the service's permissions and confirmation flow. If a connection fails or an outcome is unclear, verify its state before submitting the same operation again.

Add a custom MCP server

Select Add Connector to open Add custom MCP. The resulting server is user-level and its configuration is saved under mcpServers in ~/.qoder/settings.json. Choose either method:
  • Form: enter an MCP name, choose a transport, and complete the fields shown for that transport.
  • JSON: paste a complete MCP server configuration after reviewing its command, arguments, URL, and environment-variable names.

Set a tool call timeout

After choosing a transport in the custom MCP form, optionally set Timeout (milliseconds, optional) to control how long Qoder waits for one tool call. 60000 means 60 seconds. Use an integer from 1000 to 2147483647, or leave it empty for the default policy. In JSON, add "timeout": 60000 to the existing server entry while retaining its command, URL, and other fields. This field example is not a complete server configuration. A timeout does not establish that a remote operation was canceled or rolled back. For calls that write data, check the actual result before retrying. Select Add MCP only after confirming the configuration. Do not place secrets in task instructions or commit them to a repository; use the authentication or environment mechanism supported by the server.

Use a Connector in a task

Describe the external system, intended action, and scope in your task. To choose a connector explicitly, type / and select it from the connector suggestions. Qoder may request approval before a tool call, depending on the current access-permission setting and the requested action.

Connector updates and cloud configuration

Qoder can check eligible marketplace or enterprise connector extensions for updates. Plugin-provided connectors update through their parent plugin. A manually entered MCP connection is not a marketplace extension update target. Cloud Agents use separate cloud resource configuration. Local sync accepts independently configured user-level HTTPS connectors. It excludes stdio, plugin-provided and AppHub-managed connectors, static headers, and URLs with query parameters.

Verify and troubleshoot

  1. Confirm that the Connector is installed and any required account authorization is complete.
  2. Ask for a small read-only operation and verify the returned account, project, or workspace.
  3. For a custom MCP server, check the transport, command or URL, arguments, environment variables, and network access.
  4. Retry only after the server's tool list loads successfully.
If a write fails, do not immediately broaden permissions. First confirm the target, connector account, and service-side authorization.