For the complete documentation index, see llms.txt. This page is also available as Markdown.

Authentication patterns

MCP integrations can use either token/bearer authentication or OAuth authorization codes, based on the vendor's required authentication method.

Token/bearer authentication

Use when the vendor provides a static token or API key. The user configures the token, and the integration uses it for all requests. test-module works directly with client.test_connection(). For an example, see Packs/GitHubMCP/Integrations/GitHubMCP .

OAuth authorization code

Use when the vendor requires user authorization via OAuth. The user runs generate-login-url to get an authorization URL, authorizes the integration, and provides the authorization code. test-module raises an exception directing users to use auth-test instead. For an example, see Packs/CloudFlareMCP/Integrations/CloudFlareMCP .

OAuth dynamic client registration

Use when the vendor supports automatic client registration. This option is similar to OAuth authorization code, but the Client class handles registration automatically. For an example, see Packs/AtlassianCloudMCP/Integrations/AtlassianCloudMCP .

Multiple auth types (generic)

Use when you need to support multiple authentication methods in a single integration. Include an auth_type dropdown parameter and validate that required parameters are present for the selected auth type.

Last updated

Was this helpful?