> ## Documentation Index
> Fetch the complete documentation index at: https://connect.watson-orchestrate.ibm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server Integration (Paid Listing)

## Overview

The Model Context Protocol (MCP) server integration allows builders to add partner Remote MCP servers directly from the watsonx Orchestrate catalog to their agents. This guide covers the submission process for **paid listings** where pricing and billing are managed through IBM.

<Note>
  Looking for BYOL (Bring Your Own License) instructions? See [MCP Server BYOL Integration](./mcp-server-byol).
</Note>

## Quick Start: Accessing the Paid Listing Form

To begin submitting your paid MCP server listing:

1. Navigate to the **IBM Concierge** platform
2. Go to the **My AI products** page
3. Click the **Create** button
4. Select **Create a paid listing** in the License type section
5. Select **MCP Server** as the Product type
6. Follow the detailed steps below to complete your submission

<Note>
  Paid listings require completing a checklist and IBM approval before publishing. The entire process typically takes 5-7 business days for approval, plus up to 3 weeks for the MCP server to appear in the catalog.
</Note>

## Prerequisites

Before submitting your MCP server, ensure you have:

* **Remote MCP server**: A functioning Remote MCP server endpoint
* **APP\_ID**: Unique identifier provided by IBM Ecosystem team (obtained via email)
* **Test credentials**: Valid credentials for IBM to create test connections
* **Documentation**: Setup documentation and at least one use case for testing
* **Authentication**: Supported authentication schema configured (OAuth2, API Key, Bearer Token, Basic Auth, or Key-Value)
* **Icon**: Square icon for your application (max size 200×200px)

## Supported Authentication Schemas

The MCP server supports all authentication schemas available in the watsonx Orchestrate platform:

* **OAuth2** (without Dynamic Client Registration)
* **API Key**
* **Bearer Token**
* **Basic Auth**
* **Key-Value**

For detailed authentication implementation guidance, see the [Remote MCP Toolkits documentation <Icon icon="arrow-up-right-from-square" iconType="solid" />](https://developer.watson-orchestrate.ibm.com/tools/toolkits/remote_mcp_toolkits).

## Obtaining Your APP\_ID

Before you can submit your MCP server through Concierge, you need to obtain an APP\_ID from the IBM Ecosystem team.

### Request Process

Contact the IBM Ecosystem team to request your APP\_ID:

* **Email**: **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)**
* **Subject**: "MCP APP\_ID Request - \[Your Company Name]"
* **Include**:
  * Company name
  * MCP server name
  * Brief description
  * Submission type: **Paid Listing**

The IBM Ecosystem team will respond via email with your unique APP\_ID. This APP\_ID is required when configuring your MCP server in the Concierge platform.

<Note>
  **Important**: Save the APP\_ID from the email response. You will need it when filling out the product details in Concierge.
</Note>

## Submission Process

### Step 1: Create Your MCP Server Product

<Steps>
  <Step title="Access IBM Concierge">
    Navigate to the IBM Concierge platform and go to the **My AI products** page.
  </Step>

  <Step title="Click Create button">
    Click the **Create** button to start creating a new AI product.
  </Step>

  <Step title="Select license type">
    In the **License type** section, select **Create a paid listing**.

    Click **Next** to continue.
  </Step>

  <Step title="Select product type">
    In the **Product type** section:

    1. Select **MCP Server**
    2. Click **Next**
  </Step>

  <Step title="Provide product details">
    In the **Product details** section:

    * **Display name**: Enter a user-friendly name for your MCP server
    * **Programmatic name**: Programmatic name is automatically derived from the display name

    <Warning>
      **Naming Requirements:**

      **Display Name** - Allowed characters:

      * Lowercase letters: `a-z`
      * Numbers: `0-9`
      * Space: ` `
      * Forward slash: `/`
      * Parentheses: `(` `)`
      * Period: `.`
      * Hyphen: `-`
    </Warning>

    Click **Next** to continue.
  </Step>

  <Step title="Review and create">
    Review your product details and click **Create** to create your MCP server product.
  </Step>
</Steps>

### Step 2: Configure Your MCP Server

After creating your product, you'll be able to edit and configure all the details.

<Steps>
  <Step title="Basic information">
    Configure the basic product information:

    * **Name**: Validate the programmatic MCP server name (provided during creation)
          <Note>
            The programmatic name cannot be edited. You can only validate that it's correct. If it needs to be changed, contact **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)**.
          </Note>
    * **Display Name**: User-friendly name for the catalog tile
    * **Description**: Detailed description of your MCP server capabilities and features
    * **Version**: MCP version (e.g., "1.0.0")
    * **Change log**: Document changes in this version
  </Step>

  <Step title="Categorization and language">
    Configure categorization and language support:

    * **Domain tags**: Select 1-3 catalog categories:
      * Customer Care
      * Finance
      * Healthcare
      * HR
      * Legal
      * News
      * Procurement
      * Productivity
      * Research
      * Sales
      * Security
      * Talent Management
    * **Language support**: Select all supported languages (e.g., English)
  </Step>

  <Step title="Application details">
    Configure application-specific settings:

    * **Application ID**: Enter your APP\_ID (received via email from IBM Ecosystem team)
    * **Application Name**: Your company name (recommended for searchability, though you can use any name)
    * **Application icon**: Upload your square icon (max size 200×200px)

    <Note>
      **Application Name**: It's best to use your actual company name to make your MCP server easily searchable in the catalog.
    </Note>
  </Step>

  <Step title="MCP server configuration">
    Provide your MCP server endpoint configuration:

    * **Server end-point URL**: Your Remote MCP server endpoint URL
    * **Transport**: Select transport type:
      * Streamable HTTP
      * SSE
  </Step>

  <Step title="Configure authentication">
    Click the **Connect** button to provide authentication details for your MCP server:

    * Select your authentication schema (OAuth2, API Key, Bearer Token, Basic Auth, or Key-Value)
    * Provide the required credentials and configuration for the selected schema
    * Test the connection to ensure it works correctly
  </Step>

  <Step title="Add related links">
    Under **Related links**, click **Add custom links** to provide:

    * **Support** (required): Link to your support resources
    * **Terms and Conditions** (required): Link to your end-customer EULA
    * **Documentation** (optional): Link to setup and usage documentation
    * **Demo** (optional): Link to demo video or materials
    * **Training** (optional): Link to training materials
  </Step>

  <Step title="Save your configuration">
    Click **Save** to save your MCP server configuration.
  </Step>
</Steps>

### Step 3: Complete Checklist and Submit for Approval

For paid listings, you must complete a checklist before publishing:

<Steps>
  <Step title="Review the checklist">
    Review the checklist in Concierge to see what needs to be completed. The checklist will include items such as:

    * Validating the programmatic name
    * Providing all required information
    * Completing documentation requirements
    * Providing test credentials and use cases
  </Step>

  <Step title="Complete all checklist items">
    Work through each item in the checklist:

    * Ensure all required fields are populated
    * Validate that the programmatic name is correct
    * Provide comprehensive documentation
    * Submit test credentials for IBM validation
    * Include at least one use case for testing
  </Step>

  <Step title="Submit for approval">
    Once all checklist items are completed, submit your MCP server for IBM approval.
  </Step>

  <Step title="Wait for IBM validation">
    IBM will validate your submission:

    1. Review submission completeness
    2. Validate functionality and connectivity
    3. Test use cases with provided credentials
    4. Approve for catalog listing

    **Timeline**: Validation typically takes 5-7 business days
  </Step>

  <Step title="Publish after approval">
    Once IBM approves your submission, you can click **Publish** to initiate the publishing process.

    <Warning>
      **Publishing Timeline**: After clicking Publish, your MCP server will go through the watsonx Orchestrate release pipeline. It can take **up to 3 weeks** for your MCP server to appear in the catalog.
    </Warning>
  </Step>
</Steps>

## What Happens After Publishing

Once your MCP server is published and appears in the catalog:

1. **Catalog listing**: Your MCP server appears in the watsonx Orchestrate catalog as a distinct listing type

2. **Builder access**: Builders can discover and add your Remote MCP server to their agents directly from the catalog

3. **Connection management**: Builders configure connections using the authentication schema you specified

4. **Usage tracking**: Monitor adoption and usage through IBM Ecosystem team reports

5. **IBM-managed billing**: Pricing and billing are handled through IBM's systems

## Updating Your MCP Server

To update your MCP server listing:

1. Access your MCP server product in IBM Concierge
2. Navigate to the **My AI products** page
3. Select your MCP server product
4. Update the relevant fields:
   * Increment the version number
   * Update description, documentation links, or other details
   * Add notes to the change log explaining the updates
5. Click **Save**
6. Complete any checklist items if required
7. Submit for IBM approval
8. Once approved, click **Publish**

<Note>
  Updates follow the same approval process as initial submissions. Allow 5-7 business days for validation, plus up to 3 weeks for the update to appear in the catalog after publishing.
</Note>

<Note>
  If you've lost your APP\_ID, contact **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)** with your MCP server name to retrieve it.
</Note>

## Troubleshooting

### Common Issues

**APP\_ID not received:**

* Contact **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)** with subject "APP\_ID Request - \[Company Name]"
* Allow 2-3 business days for APP\_ID assignment

**Naming validation errors:**

* Verify programmatic name uses only allowed characters: `a-z`, `0-9`, `-`, `.`
* Verify display name uses only allowed characters: `a-z`, `0-9`, space, `/`, `(`, `)`, `.`, `-`

**Concierge form validation errors:**

* Ensure all required fields are populated
* Check that APP\_ID matches the one provided by IBM via email
* Validate URLs are properly formatted and accessible
* Verify icon file meets size and format requirements

**Authentication connection failures:**

* Confirm test credentials are valid and not expired
* Verify authentication schema matches your MCP server configuration
* Check that credentials have appropriate permissions
* Test connection manually before saving

**MCP server endpoint issues:**

* Ensure MCP server endpoint is publicly accessible
* Verify transport type (Streamable HTTP or SSE) is correctly specified
* Check firewall and security settings allow IBM access
* Test endpoint connectivity from external networks

**Checklist completion:**

* Review all checklist items carefully
* Ensure programmatic name is validated (not edited)
* Provide all required documentation and testing materials
* Contact **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)** if you're unsure about any checklist item

**Publishing blocked:**

* Complete all checklist items
* Wait for IBM approval (5-7 business days)
* Check for any validation errors in the form
* Ensure all required fields have been saved

**MCP server not appearing in catalog:**

* Remember that it can take up to 3 weeks after publishing for your MCP server to appear
* Check the watsonx Orchestrate release schedule
* Contact **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)** if it's been longer than 3 weeks

## Need Help?

For questions or support:

* **Email**: **[IBMAgentConnect@ibm.com](mailto:IBMAgentConnect@ibm.com)**
* **Subject format**: "MCP Support - \[Your Company Name] - \[Issue Type]"
* **Include**: MCP server name, APP\_ID, error messages, and relevant details

**Useful resources:**

* [Remote MCP Toolkits Documentation <Icon icon="arrow-up-right-from-square" iconType="solid" />](https://developer.watson-orchestrate.ibm.com/tools/toolkits/remote_mcp_toolkits)
* [MCP Server BYOL Integration](./mcp-server-byol)
* [AI Product Onboarding](./onboard)
* [IBM Support](https://www.ibm.com/docs/en/watsonx/watson-orchestrate/base?topic=notes-getting-help-support)