Skip to main content
Glama
729,588 tools. Updated 2026-10-31 19:48

"A server for finding information about PostgreSQL database" matching MCP tools:

  • Decode a database error and get the fix and the next step — no connection needed. Paste a MySQL error number (1213, 1062, 1452, 1205…) or a PostgreSQL SQLSTATE (40P01, 23505, 53300…), optionally with the failing statement, and get the proximate cause, the concrete fix, and — when it helps — the SIXTA tool and artifact to go deeper (e.g. a deadlock → paste SHOW ENGINE INNODB STATUS for sixta_explain_deadlock). Use when the user pastes a DB error code or message. Input is analyzed in memory and never stored.
    ConnectorOAuth
  • Create a database user for a Cloud SQL instance. * This tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * When you use the `create_user` tool, specify the type of user: `CLOUD_IAM_USER`, `CLOUD_IAM_SERVICE_ACCOUNT`, or `BUILT_IN`. * By default the newly created user is assigned the `cloudsqlsuperuser` role, unless you specify other database roles explicitly in the request. * You can use a newly created user with the `execute_sql` tool if the user is a currently logged in IAM user. The `execute_sql` tool executes the SQL statements using the privileges of the database user logged in using IAM database authentication. The `create_user` tool has the following limitations: * To create a built-in user with password, use the `password_secret_version` field to provide password using the Google Cloud Secret Manager. The value of `password_secret_version` should be the resource name of the secret version, like `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secrets/my-password-secret/versions/latest`. The caller needs to have `secretmanager.secretVersions.access` permission on the secret version. * The `create_user` tool doesn't support creating a user for SQL Server. To create an IAM user in PostgreSQL: * The database username must be the IAM user's email address and all lowercase. For example, to create user for PostgreSQL IAM user `example-user@example.com`, you can use the following request: ``` { "name": "example-user@example.com", "type": "CLOUD_IAM_USER", "instance":"test-instance", "project": "test-project" } ``` The created database username for the IAM user is `example-user@example.com`. To create an IAM service account in PostgreSQL: * The database username must be created without the `.gserviceaccount.com` suffix even though the full email address for the account is`service-account-name@project-id.iam.gserviceaccount.com`. For example, to create an IAM service account for PostgreSQL you can use the following request format: ``` { "name": "test@test-project.iam", "type": "CLOUD_IAM_SERVICE_ACCOUNT", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM service account is `test@test-project.iam`. To create an IAM user or IAM service account in MySQL: * When Cloud SQL for MySQL stores a username, it truncates the @ and the domain name from the user or service account's email address. For example, `example-user@example.com` becomes `example-user`. * For this reason, you can't add two IAM users or service accounts with the same username but different domain names to the same Cloud SQL instance. * For example, to create user for the MySQL IAM user `example-user@example.com`, use the following request: ``` { "name": "example-user@example.com", "type": "CLOUD_IAM_USER", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM user is `example-user`. * For example, to create the MySQL IAM service account `service-account-name@project-id.iam.gserviceaccount.com`, use the following request: ``` { "name": "service-account-name@project-id.iam.gserviceaccount.com", "type": "CLOUD_IAM_SERVICE_ACCOUNT", "instance": "test-instance", "project": "test-project" } ``` The created database username for the IAM service account is `service-account-name`.
    ConnectorNo auth
  • Set an environment variable for a project. Variables are encrypted at rest (AES-256-GCM) and injected at container runtime. NOTE: DATABASE_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE are all auto-injected for the managed PostgreSQL database — you do NOT need to set any of them manually. The PORT variable is auto-managed: 8080 for auto-detected frameworks (Next.js, Node.js, Python), or auto-detected from the Dockerfile EXPOSE directive for custom Dockerfile builds. IMPORTANT: Changing env vars does NOT auto-redeploy. You must call deploy or use the redeploy API endpoint to apply changes. For Next.js apps, NEXT_PUBLIC_* variables must be set BEFORE deploying since they are embedded at build time.
    Connector
    Destructive
    No auth
  • Reconstruct a database deadlock from the raw dump — no connection needed. Paste the LATEST DETECTED DEADLOCK section of MySQL's SHOW ENGINE INNODB STATUS, or a PostgreSQL 'deadlock detected' log entry, and get: which transaction held and waited for which lock, the inconsistent lock-ordering that caused the cycle, which transaction was rolled back, and the consistent-ordering / short-transaction / retry fix. Use when the user pastes a deadlock dump or asks 'why did this deadlock'. Input is analyzed in memory and never stored.
    ConnectorOAuth
  • List a saved schema's database registrations, linked schemas, options and sync hosts. Returns pending and quarantined delta counts, projection_upgrade_pending and database links. No LLM call. Pending zero alone does not prove healthy delivery: check quarantine and migration blockers. Use list_entity_states for server-side rows and get_record for per-record delivery state. PostgreSQL, MySQL and SQLite delivery is performed by the user's sync client. See enricher://docs/database-sync.
    ConnectorOAuth
  • Provision a managed PostgreSQL database for an app. THIS RETURNS BEFORE THE DATABASE EXISTS: the work is queued, and the app's DATABASE_URL is injected when provisioning completes. The database does not exist until get_app_database reports status `ready` (poll get_app_database for it), and the app needs a redeploy afterwards to pick up the connection. There is no tool to remove a database; removal is a console action because it destroys data.
    Connector
    Destructive
    OAuth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT

Matching MCP Connectors

  • Hosted PostgreSQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

  • About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.

  • Get information about the current user. Use this tool when: - You need to know who the current user is (email, locale, roles) before tailoring a response For information about the current fynk account, use get-account-info
    ConnectorOAuth
  • Get information about the current user. Use this tool when: - You need to know who the current user is (email, locale, roles) before tailoring a response For information about the current fynk account, use get-account-info
    ConnectorOAuth
  • Run a read-only PostgreSQL query (SELECT only) on the tables of one project. Use it for counts, sums, grouping and reads that join several tables. Use database names, not display names or IDs: - Table: the dbTableName from get-tables-meta, already in "schema.table" form; quote each part, e.g. FROM "bseXXX"."tblYYY" - Column: the dbFieldName from get-fields, in double quotes, e.g. "Status" - System columns: "__id", "__auto_number", "__created_time", "__last_modified_time", "__created_by", "__last_modified_by" Add LIMIT 100 to queries that return rows. Timestamps are stored in UTC; convert with timezone('Asia/Shanghai', "col") when needed.
    ConnectorOAuth
  • Checks if a Cloud SQL for PostgreSQL instance is ready for a major version upgrade to the specified target version. The `target_database_version` MUST be provided in the request (e.g., `POSTGRES_15`). This tool helps identify potential issues *before* attempting the actual upgrade, reducing the risk of failure or downtime. This tool is only supported for PostgreSQL primary instances and does not run on read replicas. The precheck typically evaluates: - Database schema compatibility with the target version. - Cloud SQL limitations and unsupported features. - Instance resource constraints (e.g., number of relations). - Compatibility of current database settings and extensions. - Overall instance health and readiness. This tool returns a long-running operation. Use the `get_operation` tool with the operation name returned by this call to poll its status. IMPORTANT: Once the operation status is DONE, the detailed precheck results are available within the `Operation` resource. You will need to inspect the response from `get_operation`. The findings are located in the `pre_check_major_version_upgrade_context.pre_check_response` field. The findings are structured, indicating: - INFO: General information. - WARNING: Potential issues that don't block the upgrade but should be reviewed. - ERROR: Critical issues that MUST be resolved before attempting the upgrade. Each finding should include a message and any required actions. Addressing any reported issues is crucial before proceeding with the major version upgrade. If `pre_check_response` is empty or missing, it indicates that no issues were identified during the precheck. Running this precheck does not impact the instance's availability.
    ConnectorNo auth
  • Search Cochrane systematic reviews via PubMed. Finds Cochrane Database of Systematic Reviews articles matching your query. Returns PubMed IDs, titles, and publication dates. Use get_review_detail with a PMID to get the full abstract. Args: query: Search terms for finding reviews (e.g. 'diabetes exercise', 'hypertension treatment', 'childhood vaccination safety'). limit: Maximum number of results to return (default 20, max 100).
    ConnectorNo auth
  • Find info about notable/historic landmarks, towns, and remarkable sites near a coordinate. USE FOR: - "What's near Predjama Castle?" - "Notable landmarks around Ljubljana center" - "Tell me about places near 46.05, 14.51" - Finding historic, cultural, or geographic summaries for an entire area at once. - DO NOT iterate over the results to query individual items again. - One call is sufficient to answer the user's broad geographic inquiry. Combine the results into a single comprehensive summary for the user immediately. NOT FOR: directions, finding specific cafes/shops, raw geocoding.
    ConnectorNo auth
  • Register a saved schema for relational synchronization to PostgreSQL, MySQL or SQLite. Requires owner and a sync-enabled plan. Starts a billed classification job when available; returns database ID, classification_job_id or classification_skipped, stamped_keys and registration_notices. The webhook signing secret stays outside the MCP response and can be managed in the web app. The schema is initially unpublished: wait for classification, review keys/options/notices, then publish_schema before any data can sync. pk_strategy locks once the physical model ships. Owned child arrays replace previous membership, so omitted children are deleted on re-enrichment. purge_entity_state transfers custody to replicas; relay custody_warning. A connected host may provision automatically; otherwise get_database_setup_instructions starts browser-confirmed client pairing. Modeling, publication and delivery: enricher://docs/database-sync.
    ConnectorOAuth
  • Get information about the current fynk account. Use this tool when: - You need details about the active account (e.g. default document locale, signature settings) before tailoring a response - You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in) For information about the current user, use get-user-info
    ConnectorOAuth
  • Get information about the current fynk account. Use this tool when: - You need details about the active account (e.g. default document locale, signature settings) before tailoring a response - You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in) For information about the current user, use get-user-info
    ConnectorOAuth
  • Provisions a managed PostgreSQL database on a dedicated VM on your private network. Requires a recent plan_managed_datastore. For app deployments, prefer deploy_app database:'managed' so plan_deploy includes and wires the DB automatically. It is PRIVATE - reachable only from another instance on the same private network, via the DB's internal/private IP (not a public address). Get the ids from plan_managed_datastore/list_flavors/list_private_networks/list_keypairs. Provisioning takes ~5 min; poll list_databases until status='ready', then the connection details (private_ip, port 5432, db_name, db_user) are populated. HIGH AVAILABILITY: pass ha:true to get THREE machines on three different physical hosts behind a load balancer with automatic failover instead of one machine: the database survives losing a machine, and nobody has to fail it over by hand. It costs about 3x the hourly rate (three machines instead of one), it provisions more slowly, and one connection string still serves the whole thing. Default is a single machine; show the user the price difference and get an explicit yes before turning HA on.
    ConnectorNo auth
  • Delete a project and all its deployments from sota.io. This action is PERMANENT and irreversible. It removes the project, all deployments, the managed PostgreSQL database, environment variables, and webhooks. The project slug will become available again after deletion.
    Connector
    Destructive
    No auth
  • Complete company information for Everstake: overview, metrics, certifications, products, clients, and contact details. Use when users need comprehensive facts about Everstake as a company.
    ConnectorNo auth
  • Search the Peptide Library research database by name, synonym or alias (fuzzy), optionally filtered by research category or research area. Returns short educational profiles with evidence level and the canonical Peptide Library URL. Use get_peptide_details for the full profile. No dosing information.
    ConnectorNo auth
  • Exports the current project's data model (MCD/ERD) in a universal format. Supported formats: 'dbml' (DBML / dbdiagram.io), 'sql-postgres' (PostgreSQL DDL — CREATE TABLE + ALTER TABLE FK), 'json-schema' (JSON Schema Draft 2020-12 with a vendor extension for relations), 'mermaid' (Mermaid ERD for documentation). Returns the serialized content + metadata (mimeType, extension, stats). 'dbml' is for transferring to dbdiagram.io, 'sql-postgres' for bootstrapping a database, 'json-schema' for driving a REST API. ⚠️ ROUND TRIP: only 'dbml', 'sql-postgres' and 'json-schema' can be re-imported (import_data_model). 'mermaid' is OUTBOUND-ONLY — it has no parser: a data model that leaves in this format does not come back, and a file edited elsewhere cannot be fed back in.
    ConnectorAPI key
  • Creates a user with a generated password, returned here once (also readable with get_database_credentials); live within seconds. Up to 30 users. It connects only to its databases (every logical database, future ones included, when databases is omitted): it reads and writes everything there and creates tables (on PostgreSQL in public too), or only reads with read_only; elsewhere it has no access. Its connection_uri points to defaultdb, or to its first database without access to defaultdb. On Valkey, an ACL user with every key and data command (no databases, no read_only). Treat the password as a secret. Scope: databases.write.
    ConnectorNo auth