Skip to content
Couchbase logo

Couchbase MCP server

NoSQL document database for modern applications

Couchbase is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
5
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
August 2026

About the Couchbase MCP server

Connect Couchbase once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Couchbase and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Couchbase tools your AI can run

Once connected, your assistant can call any of these Couchbase actions by asking in plain language.

  • Insert Document

    Create a new document. Fails if document already exists.

    8 fields

  • Upsert Document

    Create or update a document. Creates if it doesn't exist, updates if it does.

    8 fields

  • Get Document

    Retrieve a document by its ID

    5 fields

  • Delete Document

    Remove a document by its ID

    6 fields

  • Execute SQL++ Query

    Run a SQL++ (N1QL) query with optional vector search filters

    10 fields

Give your assistant Couchbase

Connect Couchbase once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Couchbase MCP, answered.

No. That is the point of it. One Activepieces server exposes Couchbase alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Couchbase in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 5 tools, including Insert Document, Upsert Document, Get Document, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.