Custom integrations and MCP
If a service is missing under Connecting services, you connect its API yourself. For a custom integration, you create the tools from the API documentation with the help of the AI. An MCP server is a third-party server that offers ready-made tools, and you select from them.
Create a custom integration
You store the base URL and credentials of an HTTPS API. The AI builds the requests to the API itself.
- Under Connections, open the tab Custom integrations.
- Click Add.
- In the dialog, paste the API documentation or upload files.
- Click Draft integration. The AI reads the documentation and fills in the form.
- Check the values and select the tools.
- Enter the credentials and save.
Create manually skips the AI and opens an empty form.
The AI suggests the name, base URL, kind of authentication, description, test path and named tools. It then adds the instructions per tool in the background. Create instructions again repeats this step. A further pass suggests only tools that do not exist yet.
You enter the credentials yourself; the AI does not know them. The integration exists only once you save.
The checkbox Additionally save the documentation as a knowledge document stores the documentation as a knowledge document in the workspace. Agents can then look up the schema there.
Fields
| Field | Meaning |
|---|---|
| Base URL | The common beginning of all endpoints. Starts with https://. |
| Authentication | None, Basic Auth (user + password), Bearer token, Custom header or Query parameter |
| Test path | GET path for the connection test. Without an entry, lowcloud tests /. |
| Fixed headers | Additional headers for every request, for example an API version. At most 20. |
The base URL must not point to local, internal or private addresses. lowcloud checks this on saving and on every call. Authorization, Host and Content-Length are reserved. You cannot set them as fixed headers.
The credentials are stored encrypted on the server. The AI never sees them. They also do not appear in the run events or in error messages.
Limits for drafting
| Limit | Value |
|---|---|
| Pasted documentation | at least 50, at most 200,000 characters |
| Files | 10 files, 20 MB each |
| Tools per draft pass | 20 |
| Time limit per pass | 3 minutes |
You can upload PDF, Word, text, Markdown, JSON, YAML, XML, scripts and CSV.
Create named tools
A named tool fixes a method and a path, for example Create invoice for POST /v1/invoices. With named tools, the AI chooses more precisely, and you assign rights at a finer level.
Every integration also has two general calls: Fetch data (GET) and Send data. With these, the AI can call any path of the API. Without named tools, agents use only these two.
- Open the integration.
- Click Add tool or Generate from API documentation.
- Fill in the fields.
The fields of a tool:
- Name, Method and Path: placeholders in the path are in curly brackets, for instance
/v1/invoices/{id}. - Description for the AI: short, what the tool is for. At most 500 characters.
- Instructions for the AI: how the tool is called, with mandatory fields, formats and example data. At most 8000 characters.
- Body format for writing methods: JSON, form data, text/XML or file upload.
Tools are saved immediately when you add, change or remove them. An integration has at most 50 named tools.
Test, edit and delete an integration
Test sends a real GET request to the test path, by the same route a run takes. On success, lowcloud reports the integration as reachable and names the HTTP status. Otherwise "Test failed" appears.
A click on the tile opens a read-only view. You change the base URL, credentials and description via Edit.
To delete, click … and then Delete.
Connect an MCP server
For an MCP server you only need its URL from the provider.
- Under Connections, open the tab MCP servers.
- Click Connect.
- Enter Name, URL and Description for the AI. The URL starts with https://.
- Choose the Sign-in: Shared access or Own account per person. With Shared access you enter the Token and, where needed, the Header name. The default is Authorization.
- Save. The detail page of the server opens.
- Click Read tools. The server reports which tools it offers.
- Tick the tools your workspace may use, and save.
Only the ticked tools are saved. lowcloud creates the server itself already when you connect it, even if the URL later does not answer.
Sign-in
- Shared access: the token is stored encrypted and applies to everyone in the workspace. Every run acts with it. The AI never sees the token.
- Own account per person: every person signs in with their own account in a sign-in window (OAuth). This works on the detail page via Sign in or under Connections in the row of the server. Every run acts with the account that its setup determines.
In both cases, whatever a step passes to a tool of the server goes to the host of the server.
Update tools
If the provider has changed something, click Read tools again. The page marks new and removed tools. New tools are not selected automatically.
Limits
| Limit | Value |
|---|---|
| Tools per server | 200. If the server offers more, lowcloud reads the first 200. |
| Time limit per call | 30 seconds |
| Response length | 20,000 characters, shortened after that |
| Response format | Text only. If a tool returns a file or an image, you see only a reference to it. |
Delete an MCP server
Delete MCP server removes the server. Agents and workflows that use its tools can then no longer be activated until the tools are removed there. A newly connected server with the same name does not necessarily restore the references.
Approvals
In a custom integration, every named tool has one of two settings:
- Reads only (runs directly)
- Writes (every call needs your approval)
The method sets a suggestion: GET becomes reading, everything else writing. After that, your choice applies. If you set a tool that changes something to reading, it runs without approval. Fetch data (GET) always reads, Send data always writes.
On an MCP server, every tool has the switch Read-only on the detail page. If it is on, the tool counts as reading and runs without approval. If it is off, the tool counts as writing and stops before execution.
The server can state that a tool only reads. This statement cannot be verified and only pre-fills the switch. What is switched on when you save applies.
For both: the approval is a default. Per agent and per step you can switch it off for an individual writing tool. lowcloud then asks once more and points out that the agent then carries out the action immediately.
Permissions
Anyone who may build (the role admin, or the former role developer) creates custom integrations and MCP servers. Without build rights, the tabs Custom integrations and MCP servers are missing. In a partner's client workspace, they are missing for the client's people as well.
Custom integrations and MCP servers belong to the workspace, not to a person. Everyone who may build sees them and uses their tools.
Only the person who connected an MCP server, or an admin of the workspace, may change and delete it. If the person who connected it has left the workspace, an admin can change the server.