Skip to main content
Version: ADONIS 19/ADOIT 20

Integration in Cursor

How to integrate the ADOxx MCP server in Cursor​

Cursor (https://cursor.com/) is an AI-powered code editor designed to act as an autonomous coding agent. It has built-in abilities to connect to external MCP servers.

This article describes how to configure Cursor to connect to the ADOxx MCP server.

Configuration​

To set up a connection to an ADOxx MCP, open the Cursor Settings (File -> Preferences -> Cursor Settings). Navigate to "Tools & MCPs" and click on "New MCP Server". This will open a JSON editor containing the MCP configuration.

Configuration using Authorization header​

A sample configuration using the ADOxx MCP server will look like this:

{
  "mcpServers": 
  {
    "adoxx": 
    {
      "url": "<ADOXX_URL>/mcp/message",
      "headers":
      {
        "Authorization": "Bearer <TOKEN>"
      },
      "type": "http"
    }
  }
}

<ADOXX_URL> is the URL at which the application is available (e.g. https://<HOST>:<PORT>/ADOxx), <TOKEN> is a generated OAuth 2 or OIDC token that can be generated via the oauth2/token or oidc/token endpoints or directly in the Authentication component on the Administration Page (https://docs.boc-group.com/adonis/en/docs/16.6/news/#oauth-20--oidc-generate-tokens--first-party-applications).

Configuration using Dynamic Client registration (OAuth2/OIDC)​

Cursor is able to use the discovery mechanisms as well as support for dynamic client registration (DCR) that ADOxx offers to connect and authenticate to the ADOxx MCP server without having to provide the explicit Authorization header directly. Prerequisite is the activation of DCR in ADOxx (see OAuth2 Dynamic Client Registration, OIDC Dynamic Client Registratrion).

A sample configuration will then look like this:

{
  "mcpServers": 
  {
    "adoxx": 
    {
      "url": "<ADOXX_URL>/mcp/message",
      "type": "http",
      "auth":
      {
        "scopes": ["profile", "openid"]
      }
    }
  }
}

Depending on how the used ADOxx product is accessed, Cursor will use either OAuth2 or OIDC for the authentication:

  • OAuth 2: If the used product is available directly at root level (e.g. http://<HOST>:<PORT>, MCP is e.g. available at http://<HOST>:<PORT>/mcp/message), Cursor will use OAuth 2. In this case, it is not necessary to provide the "auth" section with the scopes "profile" and "openid".
  • OIDC: If the used product is available at a deeper path (e.g. http://<HOST>:<PORT>/<PRODUCT>, MCP is e.g. available at http://<HOST>:<PORT>/<PRODUCT>/mcp/message), Cursor will use OIDC. In this case it is necessary, to provide the "auth" section with the scopes "profile" and "openid", as otherwise Cursor will not send any OIDC scope.

Testing the connection​

With the configurations provided above, Cursor will be able to connect to the ADOxx MCP server (either directly if the Authorization header is provided, or via authentication and grant using the browser) and fetch the list of available tools:

MCP Server Connection