Register MCP Server

Create an MCP Server asset to expose your pipeline as MCP tools for AI agents.

Before registering an MCP Server, ensure you have:

  • An MCP Server Pipeline created and validated (see Create MCP Server Pipeline)
  • A running Snaplex (Cloudplex or Groundplex) for pipeline execution
  • A load balancer configured for your Snaplex.
  • An authentication policy configured (optional but recommended for production)

You can register an MCP Server from Designer (with the Pipeline open) or from Manager. When creating from Designer, the Pipeline is automatically pre-filled.

  1. In the Designer toolbar, click the MCP Server icon to open the Configure MCP Server dialog.

    Alternatively, from Manager:

    1. Navigate to your project
    2. Click Create
    3. Select Create MCP Server
  2. Fill out the MCP Server configuration form:
    1. Specify a Name for the MCP Server.

      Use a descriptive name that identifies the purpose of this MCP Server.

    2. Enter a Description (optional).

      Describe what tools this MCP Server provides and its intended use.

    3. Specify the Pipeline source.

      When creating from Designer, the pipeline in the canvas is the default. When creating from Manager, select the pipeline to expose.

      Alternatively, choose Create new pipeline if you are creating a new MCP Server Pipeline.

    4. Select a Snaplex.

      Choose the Snaplex (Cloudplex or Groundplex) where the MCP Server Pipeline will execute.



    5. Select a Run Policy:
      • Triggered: Standard execution mode. Suitable for most workloads.
      • Ultra: Low-latency execution mode. Use for time-sensitive AI agent interactions.
      Note:
      • Ultra keeps the pipeline always running, which consumes more resources than Triggered.
      • Ultra does not support a timeout value.
      • Ultra does not support token propagation.
    6. Specify the Timeout (optional).

      Set the maximum execution time for the Pipeline. If not specified, the default timeout is used.

    7. Choose an Authentication Policy.

      Select an MCP policy for authentication. Options include:

      • Anonymous Authenticator (no authentication)
      • API Key Authenticator
      • MCP OAuth2 Client Credentials Rule
      • MCP OAuth2 JWT Validator Rule

      If no suitable policy exists, see Create Authentication Policy to create one.



  3. Click Save.

    The MCP Server details page opens. Displayed are URLs you can use to invoke your MCP Server:

    Streamable HTTP URL: /mcpserver/{serverId}/mcp - Stateless HTTP transport (recommended for production)



Your MCP Server is now registered and ready to accept connections. The server is enabled by default.

To disable the MCP Server without deleting it, use the Enable/Disable toggle in Manager.

Next steps: