Percona Server for MongoDB uses GateRook’s MongoDB connector. Percona Server for MongoDB.
The screenshots show GateRook 2.0.0: the Percona Server for MongoDB form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.
1. Create a connection and enter the settings
In GateRook, open Connections, select Add connection, search for Percona Server for MongoDB, choose its card and select Continue to configure.
Prepare the Percona Server for MongoDB deployment address and a database user with read access. For a replica set, obtain the seed hosts and replica-set name from its administrator.
Use a reachable MongoDB listener and the CA certificate used by the deployment when it has a private certificate authority. Operating-system or monitoring credentials are separate from MongoDB credentials.
Enter a Name, for example percona-mongodb-demo. Your AI app uses this name to choose the connection.
Set Connect using to Connection string for a replica-set URI, preserving replicaSet and the seed hosts. Remove username and password from the URI. A single listener can use Host and port instead.
Enter User and Password, choose TLS when configured, and set Auth database in Advanced to the database where the user was created. Paste a private CA into CA certificate (PEM) and keep hostname verification enabled.
Use Load databases and select only the required Databases. In Advanced, narrow Collections the agent may read with entries such as shop.orders; replace these examples with your own database and collection names.
Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.
2. Test the connection and add it to an endpoint
Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.
A seed host may be reachable while other replica-set members are not; verify the advertised member addresses and DNS if server selection fails. For authentication errors, match the user's authentication database and mechanism to the deployment.
After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.
3. Use the connection from your AI IDE
After saving Percona Server for MongoDB on the endpoint and passing its connection test, ask your AI app to use percona-mongodb-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.
The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.
Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.
Ask your AI, for example
- “List the permitted databases and collections without changing anything.”
- “Inspect the fields and indexes of the orders collection, if it exists.”
- “Show at most 10 recent order documents, returning only status and creation time.”
| Tool | What it does | Starts as |
|---|---|---|
mongo_find | Find documents with a filter and a projection. | Read only |
mongo_aggregate | Run an aggregation pipeline. $out and $merge are refused. | Read only |
mongo_update | Update the first document matching a filter. Supports update operators or an update pipeline; upsert is optional. | Approval |
mongo_update_many | Update all documents matching a filter. The read document limit does not cap updates. Supports update operators or an update pipeline; upsert is optional. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.