Configure a connection
An MCP client receives a connection URL and key from safe configuration. Do not add a presumed route by hand: use the value created for your organization.
A server presents tools, resources, and prompts. The client should show a user which action is requested and what context will be read.
const connection = {
url: process.env.CICORA_MCP_URL,
headers: { Authorization: "Bearer " + process.env.CICORA_API_KEY },
};
// Use the connection URL issued in account API settings.Permissions and execution
- Separate read, write, and execute at the tool level.
- Validate action parameters on the integration side before execution.
- Retain a journal of call, executor, and result without secrets.
Connect in a product
Isolate every connection by organization and user so one key cannot access another context.
Check available tools at connection time and again after a permission change instead of caching them indefinitely.