MCP Servers

An MCP server connects external tools for agents: CRM systems, company APIs, databases, analytics services, or other systems that the agent can call under allowed rules.

When an MCP server is needed

• the agent needs to get data from an external system;
• the agent needs to perform an action through an external API;
• you need to connect a ready MCP server URL;
• you need to manage authorization, headers, or OAuth for an external tool.

What the server list contains

• search;
• number of found servers;
• adding a server;
• empty state;
• loading errors.

Creating a server manually

• name;
• URL;
• save.

Editing a server

• name;
• URL;
• description;
• tags;
• authorization type;
• secrets or headers;
• OAuth;
• deletion.

URL and security

• must start with http:// or https://;
• if the server is not accessible from the outside, the agent will not be able to call it.
• secrets, tokens, and headers should be entered only into protected cabinet fields;
• do not publish secrets in documentation, chat messages, or the server name.

Tags

• entered separated by commas;
• help group and search for servers.

If the server does not work

1. Check the URL and external availability of the server.
2. Check the authorization type and secrets.
3. Check whether the server is connected to the required agent.
4. Open event history or a test call if available.
5. Save the error text and attempt time for diagnostics.

Where this is in the interface

Main elements in this section:

• project settings page
• MCP servers page
• MCP server search
• create MCP server
• MCP server in the list
• MCP server form
• Settings item in the side menu