MCP

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 https //app engini io/ navigate to connections page, more information here https //app archbee com/public/preview ixqqblwfxopjg0nave78y/preview o0xoah9axzyzcoygrkm 3 click on connections on the right side bar click on mcp servers 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 click on this field to get a link to our detailed guide for mcp servers server url this is a unique, automatically generated endpoint link created by the platform click the copy icon on the right side of the field to save this url to your clipboard you will need to paste this url into your external ai clients so they know where to connect add integration – used to connect a new integration to the mcp server click on “create new integration” to add a system that hasn’t been connected to engini yet you can choose one of the existing connections from the list integration tool clicking this icon opens the integration tools modal window here, you can select or deselect specific actions from the list (such as 'monday create item' or 'monday get users' ) remove clicking this icon completely detaches the integration from this mcp server 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 install node js https //nodejs org/en/download and claude desktop https //claude com/download now click on generate new and copy the token into the bearer field (which is marked in yellow in the picture) open settings click the menu and select settings > developer open settings a new window will pop up configure mcp click edit config and paste the configuration below the following window will open, choose the following file copy what is written in server configuration (from the previous step) save the file save and restart save the config and restart claude desktop note claude has a limit of 40 mcp tools that can be enabled at a time mcp client connecting engini to mcp client enter your engini account at https //app engini io https //app engini io/ navigate to connections page, more information here https //app archbee com/public/preview ixqqblwfxopjg0nave78y/preview o0xoah9axzyzcoygrkm 3 click on connections on the right side bar click on mcp clients click on the “new mcp” option located at the top bar continue to the connection settings configuration this tab is used to define and set up the mcp client, including its name, integrations, and connected workflows 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 here https //app archbee com/docs/ixqqblwfxopjg0nave78y/cyw13 0nzzqqapxcicu2p