Skip to main content
Glama
734,550 tools. Updated 2026-11-02 06:19

"Connecting a backend project to an Elasticsearch database" matching MCP tools:

  • 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
  • Run a READ-ONLY SQL query against the project's Postgres database (SELECT, EXPLAIN, etc.) — the Floot-managed database, or an external Postgres the user connected to the project. Writes are rejected — use execute_sql for those. Returns JSON: `{rows, rowCount, command, truncated?}` (or `{results: [...]}` for multi-statement queries). Pass `database` only if the project has more than one.
    ConnectorOAuth
  • Get setup info for Rudow's client SDKs (Node.js backend, Python backend) — package name, install command, a minimal config/usage snippet, and how to obtain a project ingest API key. Use this to help a user add logging to their own codebase: install the right package for their stack and write the snippet into their code yourself — this tool only returns information, it does not install anything or touch the user's files. It never creates or reveals an ingest API key; the user must generate one manually from the dashboard (see key_instructions in the result) and paste it in themselves.
    ConnectorAPI key
  • Destructive and irreversible. Deletes a WHOLE project (by project_id): every commit and deployment, its hosts, its volumes and restore points, its managed database and bucket, and its source repository. Nothing can bring any of it back. It is the same as Delete in the project's settings on the dashboard: the project disappears from list_projects at once and the platform removes the rest in the background. confirm_name must be the project's exact name as list_projects returns it; the call is refused when it does not match, and nothing is deleted. Meant for a project the user asked by name to delete (a test app, an app made by mistake), never as cleanup the user did not ask for. To remove one commit and keep the project, use delete_commit. Requires a read-write token.
    Connector
    Destructive
    OAuth
  • Create a data connector to an EXTERNAL source the app owner controls (their own database, a REST API, or a warehouse). Returns a connector_id. Does NOT bind schemas yet. Flow: build_connect_data_source → build_discover_source (lists the tables/streams; needs this connector_id) → build_bind_data_source (bind streams to app schemas) → build_run_data_source (mode='sync' bindings only; live reads need no run). For a database you do NOT need to know the tables upfront: omit `table_names` and let discovery + bind pick them (the connector is a manual-trigger shell until bound, and a run before a sync bind is refused). Pass `table_names` only when you already know exactly which tables to sync. Credentials are sent to the platform and NEVER echoed back; prefer read-only DB creds / the Key Store for production. Requires a domain- or project-admin API key.
    ConnectorNo auth
  • Delete a project for good: its machine, its URL, anything the app kept on the machine (files it wrote, a SQLite database, uploads), its managed Postgres database if add_database gave it one, and its bucket with every file in it if add_storage gave it one. Billing stops. Even when the user asked to delete it, first reply telling them what is lost, ask them to confirm, and stop; call with confirm: true only after they answer yes. Without confirm the call refuses and nothing happens. A redeploy under the same name later gets the URL back but not the data. To take a project down later rather than now, use schedule_teardown instead. A protected project refuses it: only its owner turns protection off, on the project's page in the console, so relay the refusal instead of looking for another way.
    Connector
    Destructive
    API key

Matching MCP Servers

Matching MCP Connectors

  • Try changes on a throwaway copy of a database before making them for real. action=start makes an in-memory copy of the database. From then on EVERY call in this session on that database - reads and writes - goes to the copy, and each result begins 'TRIAL COPY of ...'. Nothing on the copy is ever saved. Check the outcome (query_aql, describe_set, get_report_data ...). Then action=discard to throw the copy away and return to the real database. To keep the changes, make the same calls again after discarding - there is no commit. action=status lists this session's trials. While any trial is on, tools whose effects would reach beyond the copy are refused: imports, create/delete database, delete report/import template, library copies, upload links, and the name history tools. Use it for a risky restructure, a bulk edit:, or a first attempt at an unfamiliar write. A copy holds the whole database in server memory - start warns when the database is large - so discard it as soon as you are done. A copy unused for 2 hours is discarded by the server; calls then fail loudly until you discard the trial here. A trial belongs to this MCP session only; another agent on the same key keeps working on the real database.
    ConnectorAPI key
  • Use this when the user wants Tailwind to automatically create Pins from their blog or RSS feed. Subscribes to a feed and assigns its Pins to one Pinterest account. This is an ongoing automation, not a one-time import: once a day, Tailwind checks the feed and drafts a SmartPin for each new post, and every generated Pin consumes SmartPin credits by its design tier — the same as a manual generation — so a busy feed drives ongoing credit use. Pins are created as drafts for review; nothing is scheduled or published automatically. Make sure the user understands that before connecting. The feed's current posts are snapshotted as the baseline, so nothing already published generates a Pin — only posts that appear after connecting do. feedUrl must be an actual feed URL: when you only have a site URL, or are not sure, call preview_feed first. accountId must be a currently connected account — a feed assigned to a disconnected one would be skipped every day without any error, so it is refused instead. A feed URL that is already connected returns a conflict error rather than a duplicate. Connecting itself spends no credits. If the user did not say which Pinterest account to use and list_accounts returns more than one, ask the user which account to use before calling this — do not choose for them.
    ConnectorOAuth
  • Generates a browser authorization URL for connecting a new social account to a project. Flow: 1. Call this tool with the `projectId` and target `platform`. Omit `redirectUrl` unless the user asks for one. 2. Give the returned `url` to the user and ask them to open it in their browser and complete the authorization. 3. Once the user says they are done, call `social_accounts_list` with the `projectId` to confirm the connected account. For Facebook, WoopSocial shows a page-selection screen after authorization. The selected pages are connected to the `projectId`.
    ConnectorOAuth
  • Run a source-free compiler smoke test through the real Axint pipeline. Use immediately after installing or connecting Axint so the current agent proves it did more than start the MCP server. Use: call immediately after install or first MCP connection; use validate or run for project checks. Inputs: format changes rendering only; the smoke test has no project inputs. Effects: read-only built-in compiler smoke test; writes no files and uses no network.
    ConnectorNo auth
  • Change how much memory an app's managed database gets. Call this when the database is slow or out of memory. db_ram_mb must be one of the sizes get_resource_usage reports under db_ram.steps_mb and fit your database-RAM pool. WARNING: the database restarts briefly to apply the new size, so the app loses its database connection for a few seconds. Only works if the app has a managed database.
    ConnectorNo auth
  • Deploy several connected services in one go (e.g. a frontend + an API). Call this when the user's project is split across multiple repos that must talk to each other; for a single repo use deploy_app. Each service is a public GitHub repo that gets its own URL. Wire them by setting an env var to the exact token ${services.<otherServiceName>.url} — Dockhold injects that service's live URL once it deploys. Give the backend its own database with "db":"enable" (DATABASE_URL is injected; a pure frontend doesn't need one). Builds run in parallel; poll get_app_status with each returned app_id.
    ConnectorNo auth
  • Create a temporary JSON database (24h TTL, no signup, no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Create once per project/task, persist the db URL immediately (local ~/.tmpstate/credentials, project README, and your memory), and reuse it instead of creating again. For retries or parallel workers, pass a stable idempotency_key so duplicate calls return the same database.
    ConnectorNo auth
  • Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
    ConnectorNo auth
  • Give this project a database, so the published site can store what visitors submit -- contact-form messages, bookings, enquiries, signups. Call this when the site needs to KEEP what visitors send rather than just email it onward, or when the user asks where their form submissions go. One database per project, created and named by Orivox; there is nothing to configure and no filename to choose. Safe to call more than once: if the project already has one, nothing is changed and ``created`` comes back False. Check ``created`` before telling the user anything was set up. ``tables`` lists what the database currently holds -- an empty list means it exists but nothing has been stored yet, which is the normal state for a site that has not been published or has had no submissions. SCOPE: this CREATES the database. To read what visitors submitted, use the query_database tool; forms store rows through the site's own data-collection contract, not through this call.
    ConnectorOAuth
  • Self-test the MCP server: reports whether the DB pool and execution receiver are reachable. Use to distinguish a backend/infra problem from a bad-input error. Returns: {status: healthy|degraded, checks: {database, receiver}}.
    ConnectorOAuth
  • Log and persist a custom activity event. Writes a permanent, non-idempotent event record to Gogi's backend database (retained indefinitely) which is displayed to the user in the UI Activity Feed / agent timeline. Repeated calls with the same details will create duplicate timeline records. WHEN TO USE: Streaming inner thoughts, reasoning steps, heartbeat signals, current status, or execution milestones to provide an audit trail of the agent's thinking process. WHEN NOT TO USE: Do NOT use this tool for reporting trades, orders, or portfolio/position queries. Standard action tools (e.g., execute_trade, close_positions, execute_prediction) automatically emit their own rich timeline events; logging them again is redundant and creates database spam.
    ConnectorOAuth
  • Start (or restart) connecting the merchant's Google Merchant Center to Pollen. Returns an authUrl that the HUMAN must open in a browser to grant Google consent - an agent cannot click it. After they approve, call get_google_connect_status to see where the flow landed (it may pause on an account picker or Terms-of-Service acceptance; resume with pick_google_account / accept_google_terms). Once active, Pollen publishes the enriched catalog automatically.
    ConnectorOAuth
  • Start (or restart) connecting the merchant's Meta (Facebook/Instagram) Business catalog to Pollen. Returns an authUrl that the HUMAN must open in a browser to approve via Facebook Login - an agent cannot click it. Afterwards call get_meta_connect_status; the flow may pause on a business or catalog picker (resume with pick_meta_business / pick_meta_catalog). Once active, Pollen publishes the enriched catalog automatically.
    ConnectorOAuth
  • Add an app to the account as one of the user's own. Takes an Apptail app_id, an App Store URL, or a name — resolved and imported the way search_apps does. Tracking starts immediately (rankings, reviews, competitors); measured downloads and proceeds still require connecting App Store Connect in the console, which cannot be done from here.
    ConnectorNo auth
  • List an agent's conversation sessions, newest first: each one's id, status, title, message count, and when it was last updated. Pass a session id to get_session to read one, or to destroy_session to delete it. Titles come from what users said to the agent and may hold personal data: quote only what the person's question needs. Sessions belong to agents; a website or app has none. Requires connecting a Valet account.
    ConnectorNo auth