Recurly Connector
Recurly is a subscription management platform designed to optimize and simplify the process of handling recurring payments and billing cycles.
RecurlyYour warehouseLive
Agent context over MCPSet up in minutes.
No code, no maintenance.
Recurly
Data source
Recurly in your warehouse.
Ready for your agents.
Recurly is a subscription management platform designed to optimize and simplify the process of handling recurring payments and billing cycles. Weld's Recurly connector is fully managed: it extracts data from Recurly, 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.
Recurly data schema.
The map your agents read.
Every table, field and relationship Weld syncs from Recurly is served to agents as context over MCP, so they pick the right tables and join on the right keys.
- tables
- 41
- fields
- 804
- relationships
- 51
Recurly models.
What the numbers mean.
Open-source SQL that turns the raw Recurly tables into the reports people ask about. Deploy them in Weld and your agent queries the definitions, not guesses.
- Billing by monthWhat was invoiced, credited, collected and still owed, by month. The cash-side companion to the MRR models, and the closest match to Recurly's invoice export totalled by month.grain: month x currency
- MRR by customer monthMRR per customer per month, and the movement that took it there: new, expansion, contraction, churn or reactivation.grain: month x customer (Recurly account) x currency
- MRR movementsThe MRR bridge by month: opening MRR, new, expansion, contraction, churn, reactivation, closing MRR, plus customer counts. The movements Recurly's subscription analytics show, rebuilt from invoiced line items.grain: month x currency
- Subscription churnEvery subscription that has ended, why it ended, and how much MRR it was carrying just before. Splits churn into customers who chose to leave and customers lost to failed payments, which the MRR bridge cannot tell apart.grain: one row per expired subscription
Ask your agent.
It already knows Recurly.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Recurly context, finds the tables it needs and queries your warehouse.
- Agent contextRecurly tables, fields and joins
- QuerySQL against your warehouse
- OperateCheck, rerun and refresh syncs
How many account rows do we have per dunning_campaign? Use our Recurly data.
Reading the Recurly context first, so the query uses the right tables and keys.
Load Recurly into any warehouse.
Set up in minutes, no code.
Everything you need.
To get started.
Recurly setup guide
Step-by-step instructions to configure and start syncing.
MCP serverConnect your agents
Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.
Weld Connect APIBuild custom connectors
Use the Weld Connect API to build and publish your own connector.
FAQCommon questions
Answers to frequently asked questions about Weld connectors.
Set it up in code.
One REST API.
Use the Weld Connect REST API to create Recurly connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.
▌Common questions.
About connectors.
Put your Recurly data to work.
Connect Recurly, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.
Source
