Clerk.io Connector

Clerk.io is an AI-powered personalization platform designed to automating product recommendations, search functionalities, and email marketing.

Start for free View documentation

4.8 on G2

Weld · Data Sources

Clerk.ioYour warehouseLive

product14 columnsSynced

category6 columnsSynced

order_product5 columnsSynced

product_category3 columnsSyncing

customer9 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Clerk.io

Data source

Authenticating...

Ready to connect

Overview

Clerk.io in your warehouse.
Ready for your agents.

Clerk.io is an AI-powered personalization platform designed to automating product recommendations, search functionalities, and email marketing. Weld's Clerk.io connector is fully managed: it extracts data from Clerk.io, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

Clerk.io data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Clerk.io is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 12
fields: 73
relationships: 2

Loading diagram…

Ask your agent.
It already knows Clerk.io.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Clerk.io context, finds the tables it needs and queries your warehouse.

Agent contextClerk.io tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextClerk.iotables12fields73joins2

How many order_product rows do we have per order? Use our Clerk.io data.

Reading the Clerk.io context first, so the query uses the right tables and keys.

●weld·search_available_references

⎿raw.clerkio.order_product

raw.clerkio.order

+ 10 more Clerk.io tables

●weld·get_reference_schema

⎿order_product · 5 columns

joins order on order_id

●weld·run_query

⎿select j.id, count(*) from {{raw.clerkio.order_product}} o

join {{raw.clerkio.order}} j on o.order_id = j.id

group by 1

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from Clerk.io data in your warehouse

>Ask about your Clerk.io dataMCP

Destinations

Load Clerk.io into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

Clerk.io setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Clerk.io connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Clerk.io ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "clerkio",
    "destination_schema_name": "clerkio_data",
    "sync_interval": "0 * * * *"
  }'
▌