שִׂיג ושִׂיח | cig.chatInstall

Summary

Creates an MCP server entry in cig.chat using its name and server URL, with optional authentication settings and tool restrictions. Custom headers can use fixed values or bot fields; test values are provided for tool listing when a header uses a bot field.

Inputs

• Name (required) — Name for the MCP server entry.
• Server URL (required) — URL of the MCP server, for example https://mcp.example.com/sse.
• Authentication — Choose None, Bearer token, or Custom headers.
• Bearer Token — Token used when Authentication is Bearer token. The UI states cig.chat stores it and never returns it.
• Custom Headers — Headers used when Authentication is Custom headers. Each header requires a name and can provide a fixed value or a bot field; the UI says to fill one of those, not both. A test value is available for listing the server's tools when a header uses a bot field.
• Allowed Tools — Tool names the agent may call. Leave empty to allow all tools.
• Request Options — Optional batching, insecure SSL certificate acceptance, HTTP proxy, and timeout settings.

Output shape

The source pack does not expose the operation implementation or response handling, so the returned shape cannot be determined.

The operation-scoped properties route the supplied server settings in the request body, but this signature-level source view does not show the API response or any additional runtime behavior.

Links

• n8n community nodes installation guide