Font Size:
Ask Joget AI

MCP Client Tool

Introduction

The MCP Client connects your agent to an MCP-compliant server and automatically exposes every tool that server offers as a callable function, with no per-endpoint configuration required.

Before you start

This tool requires a configured AI model. Set one up once in the AI Central Config plugin, then return to your agent. You also need a running MCP server with a reachable SSE endpoint before you add this tool.

What it does

MCP Client tool configuration

Model Context Protocol (MCP) is an open standard for exposing tools to AI agents over a Server-Sent Events connection. The MCP Client tool connects to any MCP-compliant server, discovers the tools it offers, and registers them all as functions the agent can call. You configure one connection; the agent gains access to every tool on that server.

The tool discovers available functions when the agent loads. If the server is unreachable at that point, the agent starts with no functions from that connection and will not retry automatically during the session.

When to use it

Use the MCP Client when you need to connect to a system that already publishes an MCP server, or when you want to expose several related operations to the agent without configuring each one individually as a JSON API Tool.

Typical scenarios include the following:

  • Project Intelligence: Connecting to a GitLab MCP server to let the agent query issues, milestones, and merge requests in natural language.
  • IT Service Desk: Connecting to a ticketing system's MCP server so the agent can look up, create, and update tickets without custom endpoint wiring.
  • ERP Integration: Connecting to an internal ERP MCP server to let procurement agents check stock levels and trigger purchase orders.
 
When not to use it
  • When the external system does not have an MCP server, use the JSON API Tool to call its REST endpoints directly.
  • When you need only one or two specific operations from an external API, a JSON API Tool instance per endpoint is simpler and easier to audit.

Get started

How to use it

To use the MCP Client Tool:

Adding the MCP Client tools

  1. Locate the MCP Client element under the Tools section of the palette.
  2. Drag and drop the File element into the Drop a tool to here section.

Configure Form Properties

To properly integrate and configure the Google Web Search, set the following fields:

  • Personalized Name: A custom name to display in the node viewer.
  • MCP Server Name: (Required) A label for this connection in the builder UI. Not shown to the agent or end user. Enter a short descriptive name, for example GitLab Project.
  • MCP Server Description: (Required) A description of the server's purpose, visible in the builder UI only. Enter plain language, for example Issues and MRs for the CRM project.
  • MCP Server SSE Endpoint: (Required) The SSE URL the tool connects to. Enter the full URL of the MCP server's streaming endpoint, for example https://mcp-server.internal/sse. Must be reachable from the Joget server, not just from your browser.
  • MCP Server Timeout: How long the tool waits for the server to respond to a tool discovery or tool execution call. Enter the number of seconds. The default is 60. Lower this if you want faster failure detection.
  • Debug Mode: Whether to write tool discovery details and execution calls to the Joget server log. Enable during setup to confirm how many tools were discovered and which functions are being called.
  • Test Connection: Button to test the MCP server connection

Best Practices

  • The SSE endpoint must be reachable from the Joget server, not from your browser. Test with the Test Connection button inside the builder, which makes the call server-side. A URL that works in your browser may be blocked by network rules on the server.
  • If the server is unreachable at agent load time, the agent starts with zero tools from this connection. The failure is silent to end users. Enable Debug Mode during setup to confirm the tool count in the server log.
  • Tool names come from the MCP server itself. The agent calls each tool by the name the server declared, not by the MCP Server Name you entered. Check the server's documentation for the names the agent will use.
  • One MCP Client instance covers one server. To connect to multiple MCP servers, add a separate MCP Client instance for each.
Created by Debanraj Ravindran Last modified by Debanraj Ravindran on Oct 11, 2026