Can AI agents automate Couchbase?

Couchbase Capella and self-managed Couchbase Server are automatable today through REST and a first-party MCP server. This record is those two cluster products. It is not MongoDB. The Capella Operational Management API at https://cloudapi.cloud.couchbase.com is a REST API for provisioning and configuration. Calls send the API key as Authorization: Bearer. Keys have roles, an allowed IP list, and an expiration date. The API is not available for free tier operational clusters, and requests are limited to 100 per minute per key. The Query Service REST API on ports 8093 and 18093 runs SQL++. POST /query/service executes statements, including data-changing statements. GET /query/service is read-only. That API accepts HTTP Basic, and it also accepts a creds parameter when a request needs more than one identity. If both are present, Basic wins and creds is ignored. Official server SDKs cover .NET, C, C++, Go, Java, Kotlin, Node.js, PHP, Python, Ruby, Rust, and Scala. couchbase-cli, cbq, cbc, cbimport, and cbexport ship with Server and in the admin or developer tools packages. couchbase-cli should match the cluster version. JavaScript libraries for SQL++ user-defined functions are managed at /evaluator/v1/libraries/{library}. Couchbase documents a self-hosted MCP server for Capella and self-managed clusters, with SQL++, key-value, schema, and health tools. Read-only mode defaults on. Enterprise support for that server is a separate Couchbase AI Data Plane license. Capella has a forever free tier operational cluster, limited to one per organization, which turns off after 72 hours of inactivity. https://docs.couchbase.com/llms.txt is a documentation index. Connector catalogs were not opened. Computer-use viability is unassessed. API, MCP, and CLI each score 7. API is the best path because it does not require a local MCP process and it is the contract the CLI and SDKs call.

Best path today: api · Overall automatability: 7/10