MCP Server

The Flogo MCP Server trigger is an implementation that facilitates connections between Large Language Model (LLM) applications (MCP Clients) and various data sources through tools, prompts, and resources. This section covers the essential configuration settings for the MCP Server, including limitations, trigger settings, handler settings, and output configurations.

Trigger Settings

Field Required Description
Trigger Settings
Server Name Yes The MCP server name.
Server Version Yes The MCP Server version.
Server Type   The following server types are supported:

  • STDIO

  • HTTP
HTTP Server Port   The port for HTTP Server. The default port is 8080.
HTTP Server Endpoint Path   Endpoint path for HTTP Server. Default is /mcp.
Enable TLS  

Enable TLS for HTTP Server. Default is False.

Note: When deploying an MCP server trigger application on TIBCO® Control Plane, set TLS to False and rely on the secure connection managed by the ingress controller.

  • Server Certificate: Path to the server certificate file (prefix with file://) or base64 encoded certificate value. For example, file:///path/to/cert.pem or MIIDXTCCAkWgAwIBAgIJALa... (base64 encoded value).

  • Server Private Key: Path to the server private key file (prefix with file://) or base64 encoded private key value. For example, file:///path/to/privatekey.pem or MIIDXTCCAkWgAwIBAgIJALa... (base64 encoded value).
Authentication Type  

The following Authentication Types are supported:

  • None

  • API Key

  • JWT Token

    Note: When configuring JWT tokens, ensure the following requirements:

    • Tokens must be signed using a symmetric algorithm.

    • The JWT payload must contain an expiration claim.
Handler Settings
MCP Primitive Type   The following MCP primitive types are supported:

  • Tool

  • Prompt

  • Resource - textResourceContent and blobResourceContent

    Note:

    • A mimeType for textResourceContent could be "text/plain".

    • A mimeType for blobResourceContent could be "image/png" or "application/pdf".

These primitives use a JSON Schema data model. You can define input arguments as JSON Schema on the Output Settings tab.
MCP Primitive Name Yes Name of the MCP primitive.
MCP Primitive Description No Description of the MCP primitive.
Resource URI Yes Set Resource URI when the primitive type is configured to Resource. You can set a static resource name (docs://readme) or a dynamic resource name (users://{id}/profile). When configuring a dynamic resource path, ensure that the corresponding JSON Schema defining path parameters are configured on the Output Settings tab.

When configuring a dynamic resource path, the path parameter is automatically generated in the corresponding JSON Schema on the Output Settings tab.

Output Settings

The Output Settings tab has the following fields:

Field Description
Schema for Arguments The JSON schema for the tool, prompt, or resource arguments.
Schema for HTTP headers The JSON schema for the HTTP headers. Configure only if you want to handle HTTP headers from tool/prompt/resource request.

Map to Flow Inputs

Use the Map to Flow Inputs tab to map the trigger output to the flow input based on the arguments JSON schema.

Flow Input Description
arguments The arguments from the trigger that you can map to flow inputs.
httpHeaders The HTTP headers from the trigger that you can map to flow inputs
tokenInfo The token information from the trigger, which includes scopes and expiration details from the JWT token, that you can map to flow inputs.

Map from Flow Outputs

Use the Map from Flow Outputs tab to map the flow output to the trigger reply.