# MCP

**Model Context Protocol (MCP)** is an emerging open standard that enables interoperability between AI agents and external tools through tool-based API interfaces. MCP allows agents to:

* Discover external tools from a registered endpoint.
* Invoke tools (APIs) dynamically based on user intent.
* Register themselves as callable tool servers (like plugins) for other agents/platforms.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-a378f97ed961d97ccd6623f8b5a46087fb87b8eb%2F0_e2mjWIjmJwo2NehC.png?alt=media" alt=""><figcaption></figcaption></figure>

Epsilla fully supports both **consuming** external MCP tool servers and **publishing** your own agent as a MCP-compatible tool server.

### Connecting Epsilla Agents to External MCP Servers

To invoke external tools via MCP inside an Epsilla agent workflow, follow these steps:

**1. Use Completion Using Tools**

From the **LLM** section, add the **Completion Using Tools** component.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-0e823a4df4cfa7735f4de2007e6b97f40c48f032%2Fcompletion%20with%20tools.png?alt=media" alt=""><figcaption></figcaption></figure>

This component is the core of an AI agent that takes user input, reasons and plans, and takes actions by using available tools.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-167806738b419d3ab84720b19cbd3ce0bb06be8a%2FScreenshot%202025-09-15%20at%2011.39.32%20AM.png?alt=media" alt=""><figcaption></figcaption></figure>

**2. Add MCP Server Component**

From the **“Add Components”** panel, expand **Tools**, and select **MCP Server**.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-3f22119c6ab8ade1090a36a13e5c3d51f58a5bee%2Ftools.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-c4a6e6fe9615f541a1011e501da39175a6a7beb5%2Fmcp%20server.png?alt=media" alt=""><figcaption></figcaption></figure>

**3. Configure MCP Server Connection**

Provide the following fields:

* **Server Name**: Friendly name (e.g., *Google Drive Connector* or *CES 2025*).
* **Server URL**: The MCP endpoint URL (e.g., `https://mcp.pipedream.net/...`).
* **Authorization Token** (if required): Token needed to access private MCP servers.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-b9b7c9cfcdf0348ee3a0839c17987635837909f7%2FScreenshot%202025-09-15%20at%2011.44.19%20AM.png?alt=media" alt=""><figcaption></figcaption></figure>

**4. Wire the Workflow**

Connect the MCP server's Tools output to the LLM component's Tools input.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-91ad4dae6837479285625ba6901b21ed0d55c856%2Fworkflow.png?alt=media" alt=""><figcaption></figcaption></figure>

The agent will now dynamically select and invoke appropriate external tools via MCP based on user queries.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-e5915f6d9b88310cbd6a618178a82ded790dbd40%2FScreenshot%202025-09-15%20at%2011.47.53%20AM.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-1f96f27987f8059b0a96fdaaf43daa78b8fcfbca%2FScreenshot%202025-09-15%20at%2011.48.05%20AM.png?alt=media" alt=""><figcaption></figcaption></figure>

### Publishing Your Epsilla Agent as an MCP Server

Epsilla allows you to **expose any agent** as an MCP-compatible tool server so it can be used by other platforms (like Cursor, Claude Desktop, **another Epsilla AI agent**, and other MCP clients).

Ensure that the access control setting is configured as "Anyone with the link."&#x20;

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-6dae57365ef8551c05797cb500ffcb34dd3fa172%2FScreenshot%202025-05-02%20at%209.07.08%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>

Once you’ve published your AI agent, you’ll see the **MCP server config** available:

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-c56cc3fdf59761753ee655fd888d8d72556a993d%2FScreenshot%202025-05-02%20at%209.08.36%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>

Copy the config snippet and paste it into your target MCP-supported platform (such as Cursor or other compatible apps).

Test the connection to confirm your agent is properly registered and discoverable.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2FT8HTdm8IHcuzLDhhOELS%2FScreenshot%202025-05-02%20at%209.09.55%20PM.png?alt=media&#x26;token=11269809-2e9b-46a3-923a-b931d5b754dc" alt=""><figcaption></figcaption></figure>

Now, your agent can be called by the other platforms as an extension to their capability.

<figure><img src="https://2532879721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM0ZX7fId7ifK45ldHWEp%2Fuploads%2Fgit-blob-b46b4efb34abd41f5ee5442502054f6bcafa3c60%2FScreenshot%202025-05-02%20at%209.13.16%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>

This integration expands your agent’s reach—letting it operate as part of a **broader AI ecosystem** with minimal setup.