Data & Storage · Integration
Couchbase Capella
Add Couchbase Capella to your product for your customers, and give your AI agents governed access to it.
Embed a Couchbase Capella integration so your customers can read and write documents in their own buckets, scopes, and collections from inside your product, with access scoped per tenant and every call audited. Document shapes differ per customer and change without notice, so mapping is configuration rather than code, and large reads are paginated and throttled for you. fastn maintains the connection so an API change is not your on-call problem.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read documents from their own Capella cluster into your product.
Create and update documents from your product so users do not need a separate database client.
Run scoped queries against a customer's collections so your product reports on their live data.
Keep access per tenant so one customer's cluster credentials are never shared with another.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries a collection to ground an answer in the customer's own data.
An agent writes or updates a document within governed permissions, with the call logged.
An agent reads a document set on a schedule and reports what changed.
Example prompt
Query the orders collection for documents created today with a status field that is still pending.
Set up Couchbase Capella in 4 steps
- 01Open the Couchbase Capella connector from your fastn dashboard.
- 02Have each customer authenticate their own Capella cluster with least-privilege credentials.
- 03Map the buckets, scopes, and collections your product may access, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Couchbase Capella integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Couchbase Capella integration without building it. Your customers connect their own Couchbase Capella account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Couchbase Capella update is not your on-call problem.
- One integration serves your product and your agents. The same governed Couchbase Capella connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
MongoDB
Redis
PostgreSQLOften used alongside
Tools the same teams tend to run next to Couchbase Capella, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceCouchbase Capella integration FAQ
How do I add a Couchbase Capella integration to my product?
Enable the Couchbase Capella connector in your fastn dashboard, then let each customer authenticate their own Couchbase Capella account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Couchbase Capella client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Couchbase Capella account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Couchbase Capella account and only ever sees their own records, datasets and fields. 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 Couchbase Capella 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 queries a collection to ground an answer in the customer's own data.
Who maintains the Couchbase Capella integration?
fastn does. When Couchbase Capella 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.
Does the Couchbase Capella integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Couchbase Capella reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Couchbase Capella integration?
A common starting point: read documents from their own Capella cluster into your product. 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 Couchbase Capella integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Couchbase Capella does not change your per-connector cost. You can start free with 3 connected accounts.
Add Couchbase Capella to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.