Developer Tools · Integration
SingleStore
Add SingleStore to your product for your customers, and give your AI agents governed access to it.
SingleStore is a distributed SQL database, and the surface this connector covers is the management API around it rather than the query path: workspace groups, the workspaces inside them, private connections, regions and organisation detail. That is the part a product needs when a customer's environment has to be created, sized, suspended while it is idle and resumed when somebody wants it, all inside their own organisation and against their own bill. The key belongs to the customer rather than to you, so a workspace your product suspends is one they explicitly authorised you to touch. Because these calls change infrastructure rather than rows, least privilege and a traceable record matter more here than throughput. fastn holds the keys per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SingleStore organisation so your product provisions a workspace for them without you holding a master key.
Suspend and resume a workspace from your product so an idle environment stops costing the customer money.
Read workspace groups, regions and private connections so your setup screens offer what that organisation genuinely has.
Read workspace state and endpoints so the rest of your product knows where a customer's database is reachable.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which workspaces are running and which have been idle long enough to suspend.
An agent resumes a suspended workspace on request, within scoped permissions and with the action attributed.
An agent explains how a customer's workspace groups and regions are laid out before anybody opens the portal.
Example prompt
Which workspaces in this organisation are running right now, and which have been idle since yesterday?
Set up SingleStore in 4 steps
- 01Enable the SingleStore connector in your fastn dashboard.
- 02Have each customer supply an API key for their own organisation, scoped to only what you actually need.
- 03Choose which workspace group and workspace operations your product exposes, and map the fields you read back.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SingleStore integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SingleStore integration without building it. Your customers connect their own SingleStore account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a SingleStore update is not your on-call problem.
- One integration serves your product and your agents. The same governed SingleStore connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Works well with
MySQL
Snowflake
AWS RedshiftOften used alongside
Tools the same teams tend to run next to SingleStore, across other categories.
Slack
Airtable
PostgreSQL
Anthropic ClaudeSingleStore integration FAQ
How do I add a SingleStore integration to my product?
Enable the SingleStore connector in your fastn dashboard, then let each customer authenticate their own SingleStore account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SingleStore client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SingleStore account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SingleStore account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this SingleStore integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which workspaces are running and which have been idle long enough to suspend.
Who maintains the SingleStore integration?
fastn does. When SingleStore changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to SingleStore events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in SingleStore?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the SingleStore integration?
A common starting point: let each customer connect their own SingleStore organisation so your product provisions a workspace for them without you holding a master key. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the SingleStore integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SingleStore does not change your per-connector cost. You can start free with 3 connected accounts.
Add SingleStore to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.