November was connector month with four new integrations covering databases, cloud storage, message queues, and the Model Context Protocol.
MCP Connector
Expose your Connic agents as MCP tools that any MCP client can call. Each linked agent becomes a tool with its name and description available via the standard MCP protocol.
The connector supports two modes:
- ✓Sync mode: MCP client waits for the agent to complete (up to 5 minutes)
- ✓Inbound mode: Fire-and-forget for longer-running tasks
Connect Claude Desktop, Cursor, or any MCP-compatible client to your Connic agents. Authentication is handled via a generated secret token.
Postgres Connector
Trigger agents from database events using PostgreSQL's LISTEN/NOTIFY mechanism. Configure a channel name, and any NOTIFY on that channel triggers your linked agents.
CREATE OR REPLACE FUNCTION notify_new_order()
RETURNS TRIGGER AS $$
BEGIN
PERFORM pg_notify(
'new_orders',
json_build_object(
'order_id', NEW.id,
'customer_id', NEW.customer_id,
'total', NEW.total
)::text
);
RETURN NEW;
END;
$$ LANGUAGE plpgsql;The connector maintains a persistent connection and automatically reconnects if dropped.
S3 Connector
Trigger agents when files are uploaded to S3. Configure via SNS or EventBridge, and your agent receives file metadata:
{
"bucket": "my-bucket",
"key": "uploads/invoice-2024-001.pdf",
"size": 245789,
"event_name": "ObjectCreated:Put",
"content": { ... } // Optional: file content
}Use prefix and suffix filters to only process specific paths or file types. Enable include_content to download and pass file contents directly to your agent (up to 10MB).
SQS Connector
Consume messages from AWS SQS queues. The connector handles visibility timeouts, automatic message deletion after successful processing, and dead letter queue routing for failed messages.
Connector Logs
Every connector now maintains a log stream accessible from the connector detail page. See:
- •Connection events (connected, disconnected, reconnecting)
- •Incoming messages with timestamps and payload previews
- •Dispatch events showing which agents were triggered
- •Errors with details for debugging
Unified Connector Management
All connectors now share a consistent create/edit UI. Configuration fields adapt to the connector type, with inline validation and clearer error messages.