Configure the MCP Connector for Claude

Configure the MCP Connector for Claude

Configuration

Set the required parameters in vars.yaml (https://github.com/figaf/Figaf-BTP-Deployment)
Add the required MCP connector configuration under ADDITIONAL_IRT_PARAMETERS.

Minimal configuration:

ADDITIONAL_IRT_PARAMETERS: --irt.mcp.connector.enabled=true
You can also set additional properties in the same way, for example:

ADDITIONAL_IRT_PARAMETERS: --irt.mcp.connector.enabled=true --irt.mcp.connector.issuer-uri=https://<qa-instance-public-url>
irt:
  mcp:
    connector:
      enabled: true

      issuer-uri: https://<your-host>

      dynamic-client-registration-enabled: false

      allowed-redirect-uris:
        - https://claude.ai/api/mcp/auth_callback

Configuration description

enabled

Enables or disables the whole MCP connector subsystem.

issuer-uri

The public HTTPS base URL that Claude uses to reach this instance.

This value becomes the OAuth issuer. All discovery, authorization, and token URLs advertised by the connector are built from this value, so it must match the hostname that Claude actually calls.

This property is required for dynamic client registration. The DCR registration_endpoint is advertised in discovery only when issuer-uri is set.

Example:

irt.mcp.connector.issuer-uri=https://<qa-instance-public-url>

dynamic-client-registration-enabled

Controls whether the open anonymous client registration endpoint, based on RFC 7591 /connect/register, is active and advertised in discovery.

When set to false(default case). Claude will not self-register. In this case, you must create the OAuth client manually from the OAuth Clients screen in the figaf tool.

This is the safest and default case.

When set to true, Claude can self-register automatically when you add the connector.

allowed-redirect-uris

Defines the allowed redirect URIs. Any client registration, manual or dynamic, is rejected if its redirect_uri is not included in this list.

By default, this should include Claude’s real callback URL:

https://claude.ai/api/mcp/auth_callback

Claude Connector Setup

1. Log in to your BTP instance

Log in to your BTP instance using your credentials.

2. Create an OAuth client

Go to the OAuth Clients section and create an authorization client with a client_id and client_secret.



3. Add the custom connector in Claude

Open:

https://claude.ai/customize/connectors

Click Add custom connector.


4. Enter the connector details

In the popup, enter the MCP endpoint:

https://<your-btp-host>/api/mcp

Then enter the client_id and client_secret created in step 3.


5. Verify the connector tools

After the connector is added, confirm that all expected tools are available in:

https://claude.ai/customize/connectors

    • Related Articles

    • How to configure landscapes

      How to configure landscapes.  It is pretty easy to create a complex landscape to handle transports in your SAP Cloud Integration/CPI landscape.  Here you can see what kinds of considerations you can have when setting up he landscape. In the video we ...

    • Configure CPI agents

      The future way to connect is the following. Here you don't need a S-User. You just need the API keys as specified below. Connecting to SAP Integration Suite /Cloud Foundry without S-User Figaf tool supports both CPI platforms: Neo and Cloud Foundry. ...

    • Configure SAP Alert Notification service

      1. Go to Service Marketplace and find Alert Notification service. 2. Finish installation wizard and create the instance. 3. Go to your alert-notification instance and configure subscriptions. 4. Create conditions based on the resources that interest ...

    • Configure PI agents

      Obtain the address to your PI System Go into the Figaf DevOps Suite and click the plus sign to add an agent Host name is how to access the system. If you are using Cloud Connecter and have deployed Figaf in BTP, you will need to use the cloud ...

    • Accessing SMTP Server using XOAUTH2 on SAP BTP

      1. Cloud Connector Flow 1.1 Define Cloud Connector Mappings Open your Cloud Connector and configure an SMTP connection to your local mail server. Click on Cloud To On-Premise and then click the Add (+) icon to create a new mapping. (screenshot 1) Map ...