SubscriptionFlow
Server Details
Read and update SubscriptionFlow billing data: customers, invoices, subscriptions and reports.
- Status
- Healthy
- Uptime
- 50.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
fetch/search form a clean pair, but sf_contact vs sf_contact_form and sf_demo_booking vs sf_request_demo are two overlapping pairs where one tool renders a form that the other submits. The descriptions acknowledge this hand-off, which helps, but an agent can still reasonably pick the form tool when it should submit (or vice versa), and sf_find_instance vs sf_connection_status both touch account existence.
Seven of nine tools share a predictable snake_case `sf_` prefix (sf_contact, sf_product_info, sf_find_instance, etc.). The two outliers, `fetch` and `search`, drop the prefix entirely, which is a minor but noticeable deviation from an otherwise consistent scheme.
Nine tools is comfortably within a healthy range for a public knowledge-base plus lead-capture server. The set is slightly padded because both form/submit pairs (sf_contact/sf_contact_form, sf_demo_booking/sf_request_demo) could be collapsed, leaving ~7 tools.
Public reading (search/fetch), product info, contact submission, demo request and instance lookup are covered, but `fetch` requires an id from a prior `search` — there is no list/browse path — and the billed domain (customers, subscriptions, invoices, payments) has zero tools, gated behind a sign-in state that is currently unavailable. Agents needing account data hit a dead end.
Available Tools
9 toolsfetchFetch a knowledge articleARead-onlyInspect
Fetch one published SubscriptionFlow knowledge article by id (an id returned by search). Draft or unknown ids are not found. Public, read-only.
Inputs: id (required).
searchSearch SubscriptionFlow knowledgeARead-onlyInspect
Search the published SubscriptionFlow knowledge base by free-text query. Returns matching articles with ids you can pass to fetch. Only published content is searchable. Public, read-only.
Inputs: query (required), limit.
sf_connection_statusCheck SubscriptionFlow sign-inARead-onlyInspect
Check whether this connection is signed in to a SubscriptionFlow account. Call it when the user asks for their own SubscriptionFlow data (customers, subscriptions, invoices, payments, billing, reports) or for a change, and no account tools are listed. Right now the connection is not signed in; the result says how to reconnect. Read-only.
Inputs: no named parameters.
sf_contactContact the SubscriptionFlow teamARead-onlyInspect
Send a message to the SubscriptionFlow team. Requires a name, work email, company and message; a phone number is optional. Returns a reference id the sender can quote. Nothing submitted is echoed back. Public, read-only.
Inputs: name (required), email (required), company (required), message (required), +1 more.
sf_contact_formShow a contact formARead-onlyInspect
Display an interactive form for getting in touch with the SubscriptionFlow team. The form collects a name, work email, company, optional phone number and a message, and submits them through sf_contact.
Inputs: no named parameters.
sf_demo_bookingBook a SubscriptionFlow demoARead-onlyInspect
Show a form to book a product demo. Collects name, email and company, then opens the scheduling page with those details pre-filled. The lead itself is captured by sf_request_demo. Public, read-only.
Inputs: no named parameters.
sf_find_instanceFind my SubscriptionFlow instanceARead-onlyInspect
Given a work email, start the enumeration- and timing-safe instance lookup. For privacy the response is deliberately generic and constant — it never confirms or denies whether an account exists; if a match is found, instructions are sent to that email. Public, read-only.
Inputs: email (required).
sf_product_infoAbout SubscriptionFlowARead-onlyInspect
Show what SubscriptionFlow does — features, the industries it serves, integrations, benefits or how pricing works. Use topic "all" to show everything at once. Public, read-only.
Inputs: topic.
sf_request_demoRequest a SubscriptionFlow demoARead-onlyInspect
Submit a request for a SubscriptionFlow demo. Validates and stores/forwards the request and returns a generic acknowledgement. Public, read-only.
Inputs: email (required), name, company, message.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read subscriptions, subscribers and orders; manage renewals, billing skips and payment links.
Read invoices, customers, items and balances; create invoices, customers and items in Billogram.
Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions.
Read Invoiced customers, invoices, payments, subscriptions; create customers, draft invoices, notes.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables read-only interaction with the FakturaXL API for querying invoices, clients, products, and stock levels with pagination, date chunking, and rate limiting.MIT

ChartMogul MCP Serverofficial
AlicenseAqualityFmaintenanceEnables interaction with the ChartMogul API to manage subscription data, customer relationships, and sales CRM activities. It allows users to retrieve key business metrics like MRR and churn while performing data operations on plans, invoices, and contacts.558MIT- AlicenseNot gradedqualityCmaintenanceEnables subscription management in a single connected Wallos account via Streamable HTTP tools — reference data lookup, search and pagination, cost summaries, upcoming payments, subscription creation and patching, tracking-state toggles, and reminder settings. Writes are idempotent and version-checked against the underlying Wallos records.24 npmDo What The F*ck You Want To Public
- AlicenseNot gradedqualityBmaintenanceEnables reading customer, subscription, transaction, and adjustment data from the Paddle Billing API to inspect billing and recurring-revenue state.324 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.