Skip to main content

Connector specification

Provide an accessible MCP service and document tools, authorization, and usage requirements.
ItemRequirement
Service addressAn accessible MCP Server URL
ToolsPurpose, parameters, and response for each tool
ImplementationValidate input, call business services, and return results or errors
OAuthComplete account authorization and callback configuration
InstructionsAccount requirements, permissions, limits, and examples

Tools and responses

Use names that describe operations. Explain input types, constraints, and required fields. Distinguish success, empty data, insufficient permissions, and service failure.

Authentication and permissions

Standalone connectors use OAuth 2.0; see Configure OAuth. Enforce permissions on the server using the authorized account, not an account identifier supplied in a tool parameter. Submit test credentials only in the dedicated review fields.

Timeouts and retries

An operation may complete even if the request times out. Check the status of an uncertain write before retrying to avoid duplication.

Before submission

Validate connection, authorization, tool calls, and error handling, and record the client and version. A standalone connector is submitted as service information, without a ZIP. Integration guide · Configure OAuth · Publish