"sql server" matching MCP tools:

• vibekit_db_queryA

  VibeKitA

  Run a read-only SQL query against an app's Postgres database and return up to 200 result rows. SELECT only — writes and DDL (INSERT/UPDATE/DELETE/ALTER/DROP/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the agent make data or schema changes. Call vibekit_db_schema first to learn the tables. SQL string, max 5000 chars.

  ConnectorNo auth

• scalix_db_text_to_sqlA

  Scalix CloudA

  Translate a plain-language question into a candidate SQL query using pattern-matching against the live schema (no AI model — simple questions only: counts, averages, filtered selects on a named table). Returns the SQL without executing it, with a confidence score; low confidence means the table was guessed. Review the statement and tables_used, then run it with scalix_db_query. For complex questions, read scalix_db_schema and write the SQL directly.

  ConnectorNo auth

• synthesize_sql_queryA

  Diogenes Autonomous Microservice GatewayA

  Translates natural language questions into dialect-accurate, optimized SQL SELECT queries with schema awareness and safety checks. Use when generating reporting queries or automated data analytics pipelines; for analyzing SQL execution performance and EXPLAIN plans, use analyze_query_plan instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'natural_language_request' and 'schema_ddl' ('sql_dialect' defaults to 'postgresql_dialect'), supports '?demo=true' or L402 (15 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth

• query_nem_dataA

  nempulseA

  Last resort for ad hoc questions the other tools cannot answer. Not for live or current prices: NEMPulse publishes daily price summaries only; use get_regional_prices for daily min/max/mean RRP and AEMO NEMWEB DISPATCHPRICE for the live 5-minute feed. Takes a plain-English question, generates SQL over NEMPulse's tables, and returns the SQL, the result rows and a short explanation. It is the slowest tool (can take close to a minute) and it is AI-generated, so check the returned SQL before relying on a number. Scope each question to about one region-month or less: wider aggregates (a full year by region, or per-day top-N across all regions) risk exceeding the 8 second SQL limit, and a longer wait does not help. For per-day top-N or bottom-N questions, ask for a window function (ROW_NUMBER or RANK) rather than a per-day subquery, which has been seen to silently return all-null rows. Queryable data: dispatch prices, daily revenue, optimal dispatch, battery price profiles and market events. The market analysis tables (monthly spreads, regressions, correlations) are not reachable here.

  ConnectorNo auth

• generate_queryA

  ALM X++ MCP ServerA

  WHEN: developer needs correct X++ select or T-SQL for D365 tables with proper joins. Triggers: 'X++ select', 'generate a query', 'SQL for', 'join with', 'how to query', 'générer une requête', 'write a select statement', 'select from', 'X++ query for', 'requête X++', 'écrire une select'. Generate both X++ select statements and equivalent T-SQL queries for D365 F&O tables. Uses real field names, relations, and indexes from the knowledge base to produce correct joins. Supports: field selection, multi-table joins (auto-detects relations), WHERE filters, ORDER BY, TOP/firstonly, cross-company. Also accepts natural language descriptions like 'find all open sales orders for customer 1001 with CustTable join'. [!] For multi-table joins, call find_related_objects (or get_relation_graph if the relation index is loaded) FIRST to get the correct FK relations -- this tool will then produce accurate join conditions. [!] The generated X++ is a template -- adapt it to your custom code context before using in production. Returns side-by-side X++ and SQL with explanations.

  ConnectorNo auth

• superdb_run_sqlA

  SuperDBA

  Executa SQL do PostgreSQL 16 (https://www.postgresql.org/docs/16/sql-commands.html) no schema do projeto SuperDB, podendo ALTERAR o banco: INSERT, UPDATE, DELETE e DDL (CREATE TABLE, ALTER, CREATE POLICY) — é o mesmo executor das migrations. Para consultas que só leem existe superdb_query_sql. SELECT sem LIMIT recebe LIMIT 1000 automaticamente; quando corta, a resposta traz "truncado": true e "limite_de_linhas": 1000 e a primeira linha avisa. Para ler mais, pagine com LIMIT/OFFSET ou keyset (WHERE id > último ORDER BY id LIMIT 1000).

  Connector

  Destructive

  OAuth

• generate_orm_modelsA

  Diogenes Autonomous Microservice GatewayA

  Compiles SQL DDL schemas into type-safe ORM entities and TypeScript validation schemas (Prisma, Drizzle, SQLAlchemy, Zod). Use when scaffolding application models, generating TypeScript data layers, or synchronizing schemas; for translating raw SQL across dialects, use transpile_sql_dialect instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'schema_ddl' ('orm_target' defaults to 'drizzle_orm_typescript'), supports '?demo=true' or L402 (15 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth

• get_query_patternsA

  Shibui FinanceA

  REQUIRED before stock_data_query, 23 SQL patterns prevent timeouts/wrong results Must be called once per session immediately after get_database_schema. Contains query patterns for time-series selection, return calculations, screening joins, window functions, backtesting, and performance optimization. Time-series queries will timeout or return wrong results without these patterns. After this tool returns, call stock_data_query to execute SQL.

  ConnectorNo auth

• get_query_patternsA

  Shibui FinanceA

  REQUIRED before stock_data_query, 23 SQL patterns prevent timeouts/wrong results Must be called once per session immediately after get_database_schema. Contains query patterns for time-series selection, return calculations, screening joins, window functions, backtesting, and performance optimization. Time-series queries will timeout or return wrong results without these patterns. After this tool returns, call stock_data_query to execute SQL.

  ConnectorNo auth

• describeA

  UltrapediaA

  What Ultrapedia holds: the queryable views, every column and what it means, the allowed values of category columns, and how many races there are. Read this before writing SQL for `query`.

  ConnectorNo auth

• import_dataA

  mcpA

  Import data into a Cloud SQL instance. If the file doesn't start with `gs://`, then the assumption is that the file is stored locally. If the file is local, then the file must be uploaded to Cloud Storage before you can make the actual `import_data` call. To upload the file to Cloud Storage, you can use the `gcloud` or `gsutil` commands. Before you upload the file to Cloud Storage, consider whether you want to use an existing bucket or create a new bucket in the provided project. After the file is uploaded to Cloud Storage, the instance service account must have sufficient permissions to read the uploaded file from the Cloud Storage bucket. This can be accomplished as follows: 1. Use the `get_instance` tool to get the email address of the instance service account. From the output of the tool, get the value of the `serviceAccountEmailAddress` field. 2. Grant the instance service account the `storage.objectAdmin` role on the provided Cloud Storage bucket. Use a command like `gcloud storage buckets add-iam-policy-binding` or a request to the Cloud Storage API. It can take from two to up to seven minutes or more for the role to be granted and the permissions to be propagated to the service account in Cloud Storage. If you encounter a permissions error after updatingthe IAM policy, then wait a few minutes and try again. After permissions are granted, you can import the data. We recommend that you leave optional parameters empty and use the system defaults. The file type can typically be determined by the file extension. For example, if the file is a SQL file, `.sql` or `.csv` for CSV file. The following is a sample SQL `importContext` for MySQL. ``` { "uri": "gs://sample-gcs-bucket/sample-file.sql", "kind": "sql#importContext", "fileType": "SQL" } ``` There is no `database` parameter present for MySQL since the database name is expected to be present in the SQL file. Specify only one URI. No other fields are required outside of `importContext`. For PostgreSQL, the `database` field is required. The following is a sample PostgreSQL `importContext` with the `database` field specified. ``` { "uri": "gs://sample-gcs-bucket/sample-file.sql", "kind": "sql#importContext", "fileType": "SQL", "database": "sample-db" } ``` The `import_data` tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes.

  ConnectorNo auth

• saved_queriesA

  ThinAir DataA

  Personal, named library of reusable SELECT queries — save once, run by name later, instead of re-pasting SQL or scanning query_history's backward-looking log. action=save stores sql under name (fails with name_exists if taken — delete first to replace). action=run executes the stored SQL through the same read-only guard and firewall as query_sql and returns up to 100 rows. action=list returns saved queries (up to 100), optionally filtered by tag. action=delete removes one by name or id. save/run/delete write to tenant storage; list is read-only. All four actions count against daily quota. Returns the saved record, a result table (run), the query list, or a delete confirmation. [BUILD tier]

  Connector

  Destructive

  OAuth

• query_firewallA

  ThinAir DataA

  Manage and test per-connection SQL firewall rules that block, warn, or log matching queries — distinct from pii_scan, which scans stored data (not SQL text) for PII. action=add_rule creates a rule (rule_name + RE2 pattern; optional block_action: block/warn/log, default block — only "block" is enforced, "warn"/"log" are advisory-only). action=remove_rule deletes by name or id. action=list_rules is read-only. action=test_query checks a sql string against the built-in guard plus your rules and returns a verdict without running it. add_rule/remove_rule write; changes take effect within 60s. All actions count against quota. Limits: 50 rules/connection, 512-char patterns. [ARCHITECT tier]

  Connector

  Destructive

  OAuth

• list_databasesA

  Bitquery: Crypto & Blockchain DataA

  CATALOG of the databases raw SQL can reach — the SHOW DATABASES equivalent. For each database: what it holds, which tool runs SQL against it, how to see its tables, and which specialized tools answer the same questions without SQL. Call it before writing raw SQL against an unfamiliar database. Takes no parameters and answers instantly. trading_rt comes first: DEX trades, OHLC / volume bars, prices and supply for every trading chain over the last ~30 days — query it with execute_sql, browse it with list_tables, describe_table and search_columns. The per-chain databases (eth_api, bsc_api, matic_api, arbitrum_api, base_api, optimism_api, robinhood_api, arc_api, tron_api, solana, bitcoin, bitcoin_flow, ripple, ripple_flow, cardano, cardano_flow, altcoin, altcoin_flow - Litecoin, Dogecoin and Dash in one database, rows told apart by blockchain_id - bitcash, bitcash_flow for Bitcoin Cash, and stellar) hold transfers, calls, events, transactions and balances; browse them with chain_list_tables, chain_describe_table and chain_search_columns (pass the database name) and query each one with that chain's <chain>_transfers_raw_sql tool (xrp_, ada_, ltc_ / doge_ / dash_, bch_ and xlm_transfers_raw_sql for the ones above after bitcoin_flow). zcash and zcash_flow are queried with zec_transfers_raw_sql but the schema browser does not cover them: that tool's description lists their tables. stellar_flow is not browsable either - it starts in December 2023 and misses some ledgers, so query stellar instead. Address labels have no SQL access at all — use the label tools. Prefer a specialized tool whenever one answers the question: it already filters on the right keys and is far cheaper than hand-written SQL.

  ConnectorOAuth

• fastero_create_queryA

  FasteroA

  Save a new SQL query against a connection so it can be scheduled, shared or turned into a report. The SQL is saved, not run; as with fastero_run_sql it must be read-only, and a statement that could change data is refused. Two queries may share a name. Returns the query with its _id, the queryId fastero_create_report and fastero_create_alert take; starting a chart from SQL, fastero_save_chart saves the query and the chart in one call. Where the query computes a business number, fastero_get_definitions holds this organisation's own expression for it, and definitionsUsed records which definitions the query was built from, with their version.

  ConnectorAPI key

• fastero_update_queryA

  FasteroA

  Change a saved query’s name or SQL text; fields not sent stay as they are, and its connection cannot be changed here. New SQL must be read-only, as for fastero_create_query. Every report, dashboard chart and alert built on the query reads the new SQL from its next run, and a chart plotting a column the new SQL no longer returns stops drawing it. The old SQL is not kept. When the SQL changes, send definitionsUsed again so it is restamped at the current version.

  Connector

  Destructive

  API key

• aws_rds_data_queryA

  Opsphere — DevOps & SRE IntelligenceC

  Run read-only SQL against Aurora via the RDS Data API (HTTPS; no VPC TCP from the MCP). Requires resourceArn (cluster) + secretArn (Secrets Manager DB credentials). Data API must be enabled. Uses the logged-in AWS session for IAM; not for classic RDS without Data API. Only SELECT/WITH/SHOW/DESCRIBE/EXPLAIN. Prefer over aws_cli_query for SQL data during incidents.

  ConnectorOAuth

• validate_sql_query_astA

  Diogenes Autonomous Microservice GatewayA

  Performs static AST syntax tree parsing on SQL statements to verify strictly read-only SELECT clauses and reject mutations, stacked queries, or comment bypasses. Use when verifying that an agent-authored SQL statement is strictly read-only before running it on a database; for screening non-SQL bash commands or general agent prompts, use verify_agent_command_safety instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'sql_statement' ('dialect' defaults to 'postgres'), supports '?demo=true' or L402 (15 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth

• validate_sql_query_astA

  Diogenes Agent Guardrails & Sandbox MCPA

  Performs static AST syntax tree parsing on SQL statements to verify strictly read-only SELECT clauses and reject mutations, stacked queries, or comment bypasses. Use when verifying that an agent-authored SQL statement is strictly read-only before running it on a database; for screening non-SQL bash commands or general agent prompts, use verify_agent_command_safety instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'sql_statement' ('dialect' defaults to 'postgres'), supports '?demo=true' or L402 (15 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth

• check_supabase_migrationsA

  VibeRavenA

  Review Supabase migration changes for missing RLS or policies, unrestricted read/write policies, exposed security definer functions and Data API grant gaps. Pass file contents: sql contains one migration's SQL text; files contains path and content for each file. Runs the VibeRaven 1.7.1 SQL rules and returns finding id, severity, file, line, a suggested fix and a guide link. For missing Data API grants, include the migration revoking default privileges or supabase/config.toml, plus browser files using supabase.from(...) (a "use client" file, or src files with package.json for Vite). Limits: supplied text only, up to 200 KB/50 files; cannot access your repository or database, does not execute SQL, and does not store or log file contents.

  ConnectorNo auth

• sanitize_sql_telemetryA

  Diogenes Autonomous Microservice GatewayA

  Masks PII, financial values, and credential literals from raw SQL query logs and slow-query dumps before telemetry storage. Use when scrubbing production database query logs before shipping to APM tools, Datadog, or external log collectors; for auditing SQL injection vulnerabilities, use audit_sql_injection_ast instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'query_logs' ('masking_policy' defaults to 'mask_pii_and_literals'), supports '?demo=true' or L402 (10 sats), and returns HTTP 400 if invalid.

  ConnectorNo auth