Billsby
Billsby is a subscription billing platform for managing customers, subscriptions, invoices, products, plans, usage counters, add-ons, and allowances.
Verdict
Common use cases
- Check subscription status during support calls
- Audit customer accounts before renewal outreach
- Pull product catalog for pricing discussions
- Verify shipping addresses for fulfillment issues
- Generate billing reports without dashboard access
Integration
- Vendor
- Billsby
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
billsby
Tools
- Create Customer
Create a Billsby customer without a subscription or payment card. This does not start recurring billing.
- Get Customer
Get billing, contact, payment-status, and account details for one Billsby customer.
- Get Subscription
Get billing schedule, customer, product, plan, pricing, status, and revenue details for one Billsby subscription.
- Get Subscription Shipping Address
Get the shipping address associated with one Billsby subscription.
- List Customers
Return one page of customers for the connected Billsby company, optionally filtered by a partial customer name.
- List Customer Subscriptions
List all subscriptions belonging to one Billsby customer.
- List Product Plans
List the plans and billing cycles configured for one Billsby product.
- List Products
Return one page of Billsby products, optionally filtered by name or visibility.
- List Subscriptions
Return one page of company subscriptions with optional status, trial, product, plan, and ordering filters.
- Update Customer
Replace the editable contact and billing-address details for an existing Billsby customer. Supply the complete desired values, not a partial patch.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Billsby in the MCP catalog and click Connect. 3. Log into your Billsby account and go to Settings > API Keys to generate a new key with read access to customers, subscriptions, and products. 4. Paste the API key into the Switchy connection form and click Authorize. 5. Switchy will verify the key by fetching your company details. 6. Once connected, open any Project and type '@Billsby list customers' to confirm the integration works. 7. If the command returns a list of customers, the MCP is ready to use. 8. To invoke a tool, @mention Billsby in a message and describe what you need — the AI will map your request to the appropriate tool and return structured data inline.
What teammates see: by default, memories from Billsby are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Customer Account Lookup
@Billsby get the customer record for Acme Corp and show me their subscription status, payment method on file, and account balance.
Subscription Audit
@Billsby list all subscriptions for customer ID 12345 and summarize the plan name, billing frequency, and next charge date for each.
Product Catalog Export
@Billsby list all products and for each one show me the available plans, billing cycles, and current pricing.
Shipping Address Check
@Billsby get the shipping address for subscription ID 67890 and confirm it matches the customer's billing address.
Customer Search by Name
@Billsby search for customers with 'Tech' in their name and return the top five results with their subscription count and account status.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@billsby list all customers with 'acme' in their name and show their current subscription status
Found 3 customers matching 'acme': Acme Corp (customer_id: cus_abc123) has 2 active subscriptions; Acme Industries (cus_def456) has 1 paused subscription; Acme Solutions (cus_ghi789) has no active subscriptions. Each record includes billing email, account creation date, and payment method status. This is an illustrative example—actual results depend on your Billsby account data.
This read-heavy example demonstrates customer search and subscription rollup. Requires API key with customer:read scope. Results are paginated; if you have hundreds of customers, you'll need to specify filters or iterate through pages. The MCP does not automatically fetch subscription details for each customer—use follow-up prompts for deeper inspection.
@billsby create a new customer named 'Beta Testing LLC' with email beta@example.com and no subscription yet
Created customer 'Beta Testing LLC' (customer_id: cus_xyz789) with email beta@example.com. Account is active but has no subscriptions or payment methods attached. You can now assign a subscription or add payment details through separate commands. This is an illustrative example—actual customer_id format depends on your Billsby configuration.
This write example shows customer provisioning without triggering billing. Useful for staged onboarding workflows where you create the account first, then attach subscriptions later. Requires customer:write scope. Note that creating a customer does not send any notification emails unless you configure webhooks or follow-up actions in Billsby.
@billsby get subscription details for sub_12345 and summarize the billing schedule, next charge date, and total revenue to date
Subscription sub_12345 belongs to customer 'Acme Corp' on the 'Pro Plan' ($99/month). Next charge: January 15, 2025. Billing cycle: monthly, started November 1, 2024. Total revenue from this subscription: $297 (3 successful charges). Current status: active. This is an illustrative example—actual revenue and dates reflect your Billsby transaction history.
This synthesis example pairs Billsby's subscription data with AI reasoning to produce a human-readable summary. Requires subscription:read scope. The MCP returns structured JSON; the AI interprets billing schedule, calculates totals, and highlights upcoming charges. Useful for customer success check-ins or finance reconciliation.
Use-case deep-dives
When customer-support teams need billing context in under 10 seconds
A 6-person support team fields 40 tickets a day where customers ask about charges, plan changes, or cancellation. The Billsby MCP wins here because Get Customer and Get Subscription pull billing status, payment history, and plan details into the chat without toggling to the Billsby dashboard. The support rep pastes a customer email, the AI returns subscription state and next billing date, and the ticket closes in one reply. This breaks down if your team needs to update subscriptions or process refunds—the MCP is read-only, so you still open Billsby for write operations. If 80% of your tickets are lookup questions and you're on API_KEY auth, this MCP cuts average handle time by 30 seconds per ticket.
When a solo founder runs churn reports without a BI tool
A bootstrapped SaaS founder with 200 customers wants to spot churn patterns every Monday morning but doesn't have a data analyst or a Looker license. The Billsby MCP is the right call: List Customers and List Customer Subscriptions feed into a prompt that groups cancellations by plan, calculates 30-day churn rate, and surfaces the top 3 plans losing subscribers. The founder gets a narrative summary in 90 seconds instead of exporting CSVs and building pivot tables. This stops working above 1,000 customers—pagination and rate limits make the MCP too slow for bulk analysis, and you'll want a proper data warehouse. Below that threshold, this MCP turns Billsby into a conversational churn dashboard.
When a 3-person sales team matches prospects to pricing tiers
A B2B SaaS sales team closes 15 deals a month and needs to recommend the right plan and billing cycle during discovery calls. The Billsby MCP's List Products and List Product Plans tools let the rep ask the AI which plan fits a prospect's usage profile—seats, feature gates, annual vs monthly—without memorizing the pricing matrix or opening a spreadsheet. The AI cross-references plan limits against the prospect's stated needs and returns a recommendation with pricing in one message. This works best when your product catalog has under 10 plans; above that, the MCP returns too much JSON for the AI to parse cleanly, and you're better off maintaining a static pricing doc. For small catalogs, this MCP turns plan selection into a 20-second conversation.
Frequently asked
What does the Billsby MCP do in Switchy?
It lets your AI agents read and create customer records, subscriptions, and product plans in your Billsby account. Agents can look up billing status, list active subscriptions, check shipping addresses, and create new customers without starting a subscription. It's useful for support workflows, billing audits, and onboarding automation where you need subscription data in context.
Do I need admin access to connect Billsby?
You need a Billsby API key, which requires account-level permissions to generate. The key grants read and write access to customers, subscriptions, and products, so only connect it if you're comfortable with agents creating customer records. If you only need read access for reporting, ask your Billsby admin to scope the key accordingly before adding it to Switchy.
Can the Billsby MCP cancel subscriptions or process refunds?
No. The available tools let you read subscription details and create customers, but they don't include cancellation, refund, or payment-processing actions. For those workflows, you'll need to handle them directly in Billsby's dashboard or use their full API outside Switchy. This MCP is best for lookup and light customer-creation tasks, not billing operations.
How is this different from querying Billsby's API directly?
The MCP wraps ten common Billsby endpoints so your agents can call them in natural language without writing code. You skip the auth boilerplate and pagination logic. If you need endpoints not covered here—like webhooks, invoices, or payment-method updates—you'll still need the raw API. For standard customer and subscription lookups, the MCP is faster to set up.
Who on the team should connect the Billsby MCP?
Whoever owns your Billsby account and can generate API keys. Since the MCP can create customers, limit access to team members who understand your billing workflows. If multiple people need subscription data in Switchy, one person should connect it and share the workspace. The connection doesn't consume extra Billsby seats or API quotas beyond normal usage.