AI and MCP
Last updated October 22, 2026·Applies to Cloud
MCP and Mera run only after you authorize them. AI clients are separate companies.
In short
- MCP uses OAuth + PKCE, scoped to the project you pick.
- We do not send database passwords to AI vendors.
- ChatGPT, Claude, and Cursor are not WoWSQL sub-processors.
Optional features
Hosted MCP and in-product AI (Mera, which uses Amazon Bedrock with Gemma) only run after you use them. We do not scan your entire database for a model unless a tool call you authorized does that.
MCP
- Connection uses OAuth with PKCE
- Access is scoped to the project you pick on the consent screen
- WoWSQL does not send database passwords to ChatGPT, Claude, Cursor, or other clients
- Query results and schema that a tool returns leave WoWSQL and go to that client
ChatGPT, Claude, Cursor, and similar products are separate controllers. Their privacy policies apply to prompts and results they receive. They are not WoWSQL sub-processors for that use. See Sub-processors.
Mera (in-dashboard AI)
Mera runs on Amazon Bedrock. Prompts and the context we send to Bedrock are processed by AWS to return an answer. Do not paste card numbers, government IDs, or secrets into Mera.
Your rules
You are responsible for SQL and other actions taken through MCP with your approval. Disable or revoke access if you do not want AI tools to touch a project. We do not currently claim a dedicated “revoke MCP” control beyond the OAuth/connection management we actually ship in the dashboard.
Questions? WoWSQL Technologies Private Limited. — legal@wowsql.com · Contact