Skip to main content
connic

MCP Server

Every agent you link becomes a tool that MCP clients can list and call. Sync mode returns the agent's answer as the tool result, and inbound mode returns a run ID for longer work.

Modes
Inbound, Sync
Set up in
Dashboard or connectors/*.yaml
Documentation
MCP Server docs
Publisher
By connic

Turn each linked agent into a tool

tools/list returns one tool per linked agent with a fixed input schema, and tools/call runs that agent.

Tool names
The agent name in lowercase, with spaces and hyphens replaced by underscores. invoice-processor becomes invoice_processor.
One input schema
A required message and an optional payload object. The keys in payload are merged into the agent's input next to message.
Tools only
The connector exposes linked agents as tools. It serves no MCP resources, prompts or subscriptions.
tools/list
{
  "name": "invoice_processor",
  "title": "invoice-processor",
  "description": "Invoke the invoice-processor 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",
        "additionalProperties": true
      }
    },
    "required": ["message"]
  }
}
agent input
{
  "message": "Extract the total and the due date.",
  "invoice_id": "INV-1042"
}

Choose between the answer and a run ID

Set the mode per connector. Sync suits questions a client wants answered in the conversation, and inbound suits work that runs longer.

Sync
The call waits for the run and returns its output as the tool result. The timeout is five minutes.
Inbound
The call returns a run ID at once while the agent works in the background. Link an outbound connector to deliver the result.
Failed runs
In sync mode, a failed, cancelled or blocked run returns a tool result with isError set to true.
Files
Send attachments in payload.files, up to 10 files and 10 MiB combined. The whole request can be up to 16 MiB.
tools/call
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "invoice_processor",
    "arguments": {
      "message": "Extract the total and the due date.",
      "payload": { "invoice_id": "INV-1042" }
    }
  }
}
sync-result.json
{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Total EUR 238.00, due 2026-10-28."
      }
    ],
    "isError": false
  }
}

Keep the MCP server next to your agents

Declare it as a YAML file in connectors/. Each deploy creates or updates it for its environment, and a rollback restores it. connic generates the endpoint URL and the secret, so neither appears in the file.

connectors/invoice-tools.yaml
type: mcp
mode: sync
name: Invoice tools
agents:
  - invoice-processor
  - invoice-checker
create: connectors/invoice-tools.yaml (mcp)

Connect current and older MCP clients

One endpoint serves the stateless 2026-07-28 protocol and earlier revisions, so clients on different protocol versions can call the same agents.

A secret in a header
Send Authorization: Bearer or X-Connic-Secret with every request. The connector has no OAuth flow and does not accept the secret in the query string.
Server-side clients
Requests with a browser Origin header are rejected, so connect native or server-side MCP clients.
One endpoint per connector
Each MCP connector has its own URL and secret. Give each client or partner its own connector, and you can pause their access separately.
Supported protocol versions
VersionTransportDiscovery
2026-07-28Stateless HTTPserver/discover
2025-11-25Streamable HTTPinitialize
2025-06-18Streamable HTTPinitialize
2025-03-26Streamable HTTPinitialize

Where an MCP server fits

Pick a setup to see what the client calls and what comes back.

Someone pastes invoice text into their MCP client, and the agent returns the checked totals as the tool result.

MCP client
Sync MCP server
invoice-processor
Checked totals in the tool result
tools/call
{
  "jsonrpc": "2.0",
  "id": 7,
  "method": "tools/call",
  "params": {
    "name": "invoice_processor",
    "arguments": {
      "message": "Extract the invoice fields and check the arithmetic.",
      "payload": {
        "text": "INV-001: subtotal EUR 200, tax 19% EUR 38, total EUR 238."
      }
    }
  }
}
sync-result.json
{
  "jsonrpc": "2.0",
  "id": 7,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Totals check out: EUR 200 plus 19% tax (EUR 38) is EUR 238."
      }
    ],
    "isError": false
  }
}

An agent in another connic project lists your pricing agent under mcp_servers and calls it like any other tool.

Agent in another project
Sync MCP server
pricing-quotes
Quote in the tool result
agents/sales-assistant.yaml
name: sales-assistant
mcp_servers:
  - name: pricing
    url: ${PRICING_MCP_URL}
    headers:
      Authorization: "Bearer ${PRICING_MCP_SECRET}"
sync-result.json
{
  "jsonrpc": "2.0",
  "id": 4,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Quote Q-3307: 25 seats on the pro plan for EUR 1,180 per month."
      }
    ],
    "isError": false
  }
}

An internal tool starts a research run, gets the run ID right away and receives the report through an outbound webhook.

Internal tool
Inbound MCP server
market-research
Report through an outbound webhook
tools/call
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "market_research",
    "arguments": {
      "message": "Compare delivery times of the five largest online furniture shops in Germany.",
      "payload": { "deadline": "2026-10-20" }
    }
  }
}
inbound-result.json
{
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Agent run started with ID: 550e8400-e29b-41d4-a716-446655440000"
      }
    ],
    "isError": false
  }
}

Each partner gets its own MCP connector and secret, so you can pause one partner without touching the others.

Partner platform
Sync MCP server
order-status
Order status in the tool result
tools/call
{
  "jsonrpc": "2.0",
  "id": 12,
  "method": "tools/call",
  "params": {
    "name": "order_status",
    "arguments": {
      "message": "Where is this order?",
      "payload": { "order_id": "ord_8812" }
    }
  }
}
sync-result.json
{
  "jsonrpc": "2.0",
  "id": 12,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Order ord_8812 shipped on October 12 and arrives on October 14."
      }
    ],
    "isError": false
  }
}

MCP Server FAQ

Native and server-side MCP clients that send the connector secret in a header. The endpoint supports the stateless 2026-07-28 protocol and Streamable HTTP 2025-11-25, 2025-06-18 and 2025-03-26. Requests with a browser Origin header are rejected.

Use sync when the caller needs the answer in the conversation. The call waits for the run and returns its output, with a five-minute timeout. Use inbound for longer work. The call returns a run ID right away, and an outbound connector can deliver the result when the run finishes.

With the connector secret, sent as Authorization: Bearer or as X-Connic-Secret. The connector has no MCP OAuth discovery or interactive authorization flow, and it does not accept the secret in the query string.

It is the opposite direction. This connector lets MCP clients call your agents. To let an agent call tools on an external MCP server, list that server under mcp_servers in the agent's YAML. The MCP server, connector and client roles explain both directions.

Yes. Put them in payload.files with name, mime_type and base64-encoded data, up to 10 files and 10 MiB combined. The whole JSON-RPC body can be up to 16 MiB, and the tool result reports accepted and omitted files under structuredContent.