OAuth lets you authorize a service by signing in and approving permissions, without entering its password in the publishing form. Standalone connectors use OAuth 2.0; plugin MCP services can also use the authorization workflow offered by the form.
Make the MCP service and authorization page accessible. Prepare an account with test permissions. Signing in to Qoder's publishing center is separate from authorizing your service.
Add these complete redirect URLs to your OAuth service allowlist. The protocol, hostname, and path must match exactly.
The current test publishing page also displays the production callback. For authorization from the publishing center, use the callback displayed on the page. For a separate test integration, use the corresponding test callback URL.
After saving, inspect the authorization request's
If the form supports test accounts, provide a dedicated account, password, service website, and reproducible instructions. Explain verification codes, organization selection, and required permissions. If neither option is available, use Unable to provide and explain the reason, service purpose, and tools. For API Key services, follow review test materials rather than OAuth callbacks.
Test approval, refusal, missing permissions, and expired authorization. If the page will not open, check service and network access. If login does not return, compare
Before integration
Make the MCP service and authorization page accessible. Prepare an account with test permissions. Signing in to Qoder's publishing center is separate from authorizing your service.
Allow callback URLs
Add these complete redirect URLs to your OAuth service allowlist. The protocol, hostname, and path must match exactly.
| Scenario | Callback URL |
|---|---|
| Production integration and authorization from the current test publishing page | https://mcp.qoder.com/api/mcp/oauth_callback |
| Separate test integration | https://mcp-test.qoder.ai/api/mcp/oauth_callback |
redirect_uri. Do not substitute the publishing page, login page, or service homepage.
Complete online authorization
- In the connector form or the plugin MCP service's review access section, choose OAuth authorization and open the login authorization page.
- Sign in to your service with a test account, check the requested permissions, and approve.
- Return to the publishing page. Check for authorization success and confirm that the returned MCP information belongs to this service.
- Connect in the client, run a representative tool call, and record the steps in your self-test report.
Other review access options
If the form supports test accounts, provide a dedicated account, password, service website, and reproducible instructions. Explain verification codes, organization selection, and required permissions. If neither option is available, use Unable to provide and explain the reason, service purpose, and tools. For API Key services, follow review test materials rather than OAuth callbacks.
Test and troubleshoot
Test approval, refusal, missing permissions, and expired authorization. If the page will not open, check service and network access. If login does not return, compare redirect_uri with the allowlist. If no success result appears, check permission approval and the publishing page's return handling. If tools fail after authorization, check account permissions, parameters, and service responses.
Report time, client version, reproduction steps, and redacted errors, without complete tokens.
Next: debug and validate · self-test report.