Connectors

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.

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.

​

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.

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.

​

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.