Generic MCP

Details

ID	`Generic MCP`
Provider	Open Source
Category	Utilities
From Version	8.13.0
Docker Image	`demisto/mcp:1.0.0.10120494`

Authentication Type (9 options)

Select the authentication method.

Basic Token Bearer Api-Key RawToken OAuth 2.0 Dynamic Client Registration OAuth 2.0 Authorization Code OAuth 2.0 Client Credentials No Authorization

Connection settings

Parameter	Name	Type	Required	Default
Server URL	`base_url`	Short text	Yes	—
Authentication Type	`auth_type`	Single select	Yes	—
Client ID	`oauth_credentials`	Credentials	No	—
Authorization code	`auth_code`	Credentials	No	—
Redirect URI	`redirect_uri`	Short text	No	`https://oproxy.demisto.ninja/authcode`
Custom headers	`custom_headers`	Long text	No	—
Authorization Endpoint	`authorization_endpoint`	Short text	No	—
Token Endpoint	`token_endpoint`	Short text	No	—
Scope	`scope`	Short text	No	—
API Token / API Key	`token`	Credentials	No	—
Username	`credentials`	Credentials	No	—
Server Name	`server_name`	Short text	No	—
Trust any certificate (not secure)	`insecure`	Boolean	No	—

Commands (4)

An MCP server publishes no fixed command set: list-tools and call-tool are the protocol plumbing, and the tools they reach are discovered from the remote server when the instance connects. The pack cannot name them ahead of time, so neither can this page.

call-tool
Calls a specific tool on the MCP server with optional input parameters.
generic-mcp-auth-test
Test the authentication configuration with the MCP server.
generic-mcp-generate-login-url
Generate an authentication login URL.
list-tools
Retrieves a list of available tools in the MCP server.

Source

GenericMCP.py GenericMCP_test.py GenericMCP.yml GenericMCP_description.md

Download History Raw

## Generic MCP Integration Description

This integration allows you to connect securely with any MCP server and access its tools in real time.

### Configuration parameters

1. **Server URL**: The base URL of the MCP server. This is a required parameter for all authentication types.

2. **Authentication Type**: Select the authentication method to use for connecting to the MCP server.

    * **Basic**: Uses a username and password for authentication.
        * **Username & Password**: Provide the username and password for basic authentication.

    * **Token**: Uses a single API token or key for authentication.
        * **API Token / API Key**: Provide the API Token or API Key to access the service REST API.

    * **Bearer**: Uses a Bearer token for authentication.
        * **API Token / API Key**: Provide the Bearer Token to access the service REST API.

    * **Api-Key**: Uses an API key for authentication.
        * **API Token / API Key**: Provide the API Key to access the service REST API.

    * **RawToken**: Uses a raw token for authentication.
        * **API Token / API Key**: Provide the raw token to access the service REST API.

    * **OAuth 2.0 Dynamic Client Registration**: Uses OAuth 2.0 Dynamic Client Registration.
        * **Authorization code**: Required to obtain the access token. To get this code, run the `!generic-mcp-generate-login-url` command and follow its instructions.
        * **Scope**: Space-separated permission identifiers requested from the authorization server.

    * **OAuth 2.0 Authorization Code**: Uses the OAuth 2.0 Authorization Code flow for authentication.
        * **Client ID**: The Client ID for your application.
        * **Client Secret**: The Client Secret for your application.
        * **Authorization code**: Required to obtain the access token. To get this code, run the `!generic-mcp-generate-login-url` command and follow its instructions.
        * **Scope**: Space-separated permission identifiers requested from the authorization server.

    * **OAuth 2.0 Client Credentials**: Uses the OAuth 2.0 Client Credentials flow for authentication.
        * **Client ID**: The Client ID for your application.
        * **Client Secret**: The Client Secret for your application.
        * **Scope**: Space-separated permission identifiers requested from the authorization server.

    * **No Authorization**: No authentication is used.

### Advanced Parameters

* **Redirect URI**: The URI to which the authorization server redirects the user-agent after granting authorization. This is typically used in OAuth 2.0 Authorization Code flow. Default: `https://oproxy.demisto.ninja/authcode`.
* **Custom headers**: Add custom headers to be sent with each API request. Enter each header on a new line in the format: `HeaderName: HeaderValue`.
* **Authorization Endpoint**: The URL for the OAuth 2.0 authorization endpoint. If not provided, the default will be the origin of the `base_url` followed by `/oauth2/authorize`. For example, if `base_url` is `https://example.com/mcp`, the default `Authorization Endpoint` will be `https://example.com/oauth2/authorize`.
* **Token Endpoint**: The URL for the OAuth 2.0 token endpoint. If not provided, the default will be the origin of the `base_url` followed by `/oauth2/token`. For example, if `base_url` is `https://example.com/mcp`, the default `Token Endpoint` will be `https://example.com/oauth2/token`.
* **Trust any certificate (not secure)**: Select this option to trust any certificate. This is not recommended for production environments.