TiDB MCP Server for AI Agents
PingCAP · Software Development
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
TiDB Cloud MCP Server brings live TiDB Cloud access into MCP-compatible agents and developer tools. It gives those clients a direct path to real schema and data, which is far more useful than asking an agent to reason from screenshots, copied DDL, or stale sample rows.
Delivered as a container image for Amazon Bedrock AgentCore Runtime, the server runs in your AWS environment and connects to the TiDB Cloud deployment you specify. You control the target cluster, the credentials, and the database privileges exposed to agents. That makes it possible to keep one deployment read-only for inspection workloads while reserving broader access for tightly controlled operational flows.
Show the rest of the publisher’s description (2 more lines)
The current toolset includes show_databases, switch_database, show_tables, db_query, db_execute, db_create_user, and db_remove_user. Together, these tools support common workflows such as schema discovery, SQL-assisted debugging, application development against live TiDB Cloud data, and selected database administration tasks carried out through the MCP interface.
This product is intended for teams that already use TiDB Cloud and want to make that database context available to AI systems without building a custom MCP layer from scratch. Buyers must provide an existing TiDB Cloud deployment, valid database credentials, and network connectivity from the runtime environment to the target endpoint. If your TiDB Cloud environment uses IP allowlists, add the required addresses before testing.
Highlights
Highlighted by the publisher on AWS Marketplace.
Give AI agents live TiDB Cloud context instead of static schema notes, exported data, or manually prepared samples.
Control which cluster, credentials, and database privileges are exposed to agents by running the MCP server in your own AWS environment.
Support schema discovery, SQL-assisted investigation, application development, and selected database operations through a single MCP server deployment.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment
Refund terms
As stated by the publisher on AWS Marketplace.
This is a free offering.
Sources
Publisher resources
2 linksLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.