Connections
MCP
10 min
learn how to connect mcp to engini to enable powerful orchestration of ai driven workflows and business system integrations mcp connects to claude ai, cursor, and windsurf, and serves as a central layer for managing advanced automation prerequisites users are required to have an account for at least one of the following tools claude, cursor, or windsurf mcp server connecting engini to mcp server enter your engini account at https //app engini io/ navigate to connections page, more information https //app archbee com/public/preview ixqqblwfxopjg0nave78y/preview o0xoah9axzyzcoygrkm 3 click on mcp servers on the right side bar click on the “new mcp” option located at the top bar after clicking on “new mcp” the following window will open on "configuration" page configuration this tab is used to define and set up the mcp server, including its name, integrations, and connected workflows server name a unique identifier for your mcp connection within engini add integration – used to connect a new integration to the mcp server click on “add integration” to add a system that hasn’t been connected to engini yet you can choose one of the existing connections from the list create a new connection by clicking “add connection” to learn more about creating a connection, https //app archbee com/public/preview ixqqblwfxopjg0nave78y/preview o0xoah9axzyzcoygrkm 3#swtww add workflow – used to attach an existing workflow to the mcp server when clicking “add workflow", a list of all available workflows that can be assigned to the mcp server is displayed, allowing you to select and associate the relevant one save mcp server – saves all configuration changes made to the server client setup the field displays three available mcps claude, cursor, and windsurf each one has a dedicated guide explaining what to enter in the mcp configuration based on the one you selected click on one of the available options to view the installation instructions note each tool has its own guide for navigating to the relevant settings, but the steps for what needs to be copied from engini into the tool are the same claude this guide provides the setup instructions for claude the setup process is divided into three main sections for clarity and ease of use generate token for each mcp connection you set up, you need to generate a token for your account to do this, click on the user profile link highlighted in blue, this will open the following window now click on generate new and copy the token into the bearer field (which is marked in yellow in the picture) server configuration in this field, you’ll find the information you need to copy into your claude account the detailed instructions are provided in the next step instructions on where to navigate within your claude account install the app from the given link open settings a new window will pop up click on developer and then click on edit config button the following window will open, choose the following file copy what is written in server configuration (from the previous step) save the file restart claude and return to engini to complete the process mcp client connecting engini to mcp client enter your engini account at https //app engini io/ navigate to connections page, more information https //app archbee com/public/preview ixqqblwfxopjg0nave78y/preview o0xoah9axzyzcoygrkm 3 click on mcp clients on the right side bar click on the “new mcp client” option located at the top bar continue to the connection settings connection name enter a unique identifier for the connection within engini this name is used to categorize and manage the specific mcp integration in your workspace base url the endpoint address of the remote mcp server this url acts as the entry point for the client to discover and interact with the server's tools and resources authorization type the authentication method required by the remote server to grant access no auth connection is established without providing credentials bearer token an encrypted string provided by the service provider to verify your identity and permissions custom header allows you to define specific, non standard header keys and values required by the server for authorization transport the communication protocol used to exchange data between the client and the server sse (server sent events) a standard allowing servers to push real time updates to the client over a single http connection stream a persistent connection using server sent events (sse) that allows for real time, asynchronous data delivery from the server to the client save settings click this button to store the configuration and initialize the connection to the remote mcp server for more information on how to use the mcp client, click https //app archbee com/docs/ixqqblwfxopjg0nave78y/cyw13 0nzzqqapxcicu2p