Connectors

MCP Server

Expose your agents as MCP tools. Link agents to the connector and they become callable tools via the MCP protocol.

Sync Mode (Recommended)

Waits for agent completion and returns the result. Best for interactive use where you need immediate feedback.

Setup Instructions

Create the connector

Open your agent, click Add inbound connector in the Connector Flow, then Create New Connector and select MCP Server.

Choose Sync mode and copy credentials

Select Sync mode and click Create. The detail drawer opens automatically with the Endpoint URL and Secret in the Configuration section. All linked agents become callable MCP tools. To view credentials later, hover over the connector in the Connector Flow and click the Eye icon.

Add to your MCP client

Paste the endpoint into your MCP client config (Claude Desktop, Cursor, or any MCP-compatible client).

Response Format

response.json

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "The invoice total is $1,234.56. Payment due: Jan 15, 2025."
      }
    ],
    "isError": false
  }
}

Timeout is 5 minutes. For longer tasks, use Inbound mode.

Configuration

Mode: Sync (wait for result) or Inbound (fire & forget)
Require Auth: Enable/disable secret key authentication (default: enabled)

When created, the connector generates a unique Endpoint URL and Secret Key.

Linked Agents as Tools

Link agents to the MCP connector from the agent detail page. Each linked agent is exposed as a tool with a standardized input schema:

tool-schema.json

// Each linked agent becomes a tool with this schema
{
  "name": "agent_name",        // Agent name (lowercase, underscores)
  "title": "Agent Name",       // Display name
  "description": "Invoke the Agent Name agent",
  "inputSchema": {
    "type": "object",
    "properties": {
      "message": {
        "type": "string",
        "description": "The message or prompt to send to the agent"
      },
      "payload": {
        "type": "object",
        "description": "Additional structured data to pass to the agent"
      }
    },
    "required": ["message"]
  }
}

Agent names are converted to lowercase with spaces replaced by underscores:Invoice Processor → invoice_processor

Calling a Tool

Use tools/call to invoke an agent:

request.json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "invoice_processor",
    "arguments": {
      "message": "Process this invoice and extract the total",
      "payload": {
        "invoice_id": "INV-12345",
        "customer": "Acme Corp"
      }
    }
  }
}

message (required): The prompt sent to the agent

payload (optional): Additional data accessible via {{payload.field}}

Authentication

Include the secret key in every request using one of these headers:

terminal

# Authorization header (recommended)
Authorization: Bearer your-secret-key

# Or X-Connic-Secret header
X-Connic-Secret: your-secret-key

If Require Auth is disabled, requests work without a secret. Only disable for trusted networks.

Supported Methods

initialize

Returns server capabilities and protocol version

tools/list

Returns all linked agents as tools

tools/call

Invokes an agent by tool name

ping

Health check, returns empty object

Inbound Mode

Returns immediately with a run ID. Agent processes in the background. Check run status via the dashboard or API.

Setup Instructions

Create the connector

Open your agent, click Add inbound connector in the Connector Flow, then Create New Connector and select MCP Server.

Choose Inbound mode and copy credentials

Select Inbound mode and click Create. The detail drawer opens automatically with the Endpoint URL and Secret in the Configuration section. To view credentials later, hover over the connector in the Connector Flow and click the Eye icon.

Connect your client

Tool calls return immediately with a run ID. Results are available in the dashboard or via an outbound connector.

Response Format

response.json

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Agent run started with ID: 550e8400-e29b-41d4-a716-446655440000"
      }
    ],
    "isError": false
  }
}

Configuration

Mode: Sync (wait for result) or Inbound (fire & forget)
Require Auth: Enable/disable secret key authentication (default: enabled)

When created, the connector generates a unique Endpoint URL and Secret Key.

Linked Agents as Tools

Link agents to the MCP connector from the agent detail page. Each linked agent is exposed as a tool with a standardized input schema:

tool-schema.json

// Each linked agent becomes a tool with this schema
{
  "name": "agent_name",        // Agent name (lowercase, underscores)
  "title": "Agent Name",       // Display name
  "description": "Invoke the Agent Name agent",
  "inputSchema": {
    "type": "object",
    "properties": {
      "message": {
        "type": "string",
        "description": "The message or prompt to send to the agent"
      },
      "payload": {
        "type": "object",
        "description": "Additional structured data to pass to the agent"
      }
    },
    "required": ["message"]
  }
}

Agent names are converted to lowercase with spaces replaced by underscores:Invoice Processor → invoice_processor

Calling a Tool

Use tools/call to invoke an agent:

request.json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "invoice_processor",
    "arguments": {
      "message": "Process this invoice and extract the total",
      "payload": {
        "invoice_id": "INV-12345",
        "customer": "Acme Corp"
      }
    }
  }
}

message (required): The prompt sent to the agent

payload (optional): Additional data accessible via {{payload.field}}

Authentication

Include the secret key in every request using one of these headers:

terminal

# Authorization header (recommended)
Authorization: Bearer your-secret-key

# Or X-Connic-Secret header
X-Connic-Secret: your-secret-key

If Require Auth is disabled, requests work without a secret. Only disable for trusted networks.

Supported Methods

initialize

Returns server capabilities and protocol version

tools/list

Returns all linked agents as tools

tools/call

Invokes an agent by tool name

ping

Health check, returns empty object

Connectors Overview

Learn about connector modes

HTTP Webhooks

Trigger agents via HTTP

Variables

Access payload data in agents

Agent Configuration

Configure agents to link