Skip to main content
Glama
698,632 tools. Updated 2026-10-24 15:13

"Using Cherry Studio Tool on Windows to Connect to MySQL MCP Server" matching MCP tools:

  • List Clerk applications connected to the authenticated Vee3 account. Returns clerk_instance_id, display name, environment type, and whether each connection is the default. Use clerk_instance_id on future Clerk calls, or omit it to use the default account. If accounts is empty, the user must connect a Clerk application at https://vee3.io/dashboard/connections before Clerk capabilities work. Agents cannot complete the connection flow; ask the user to connect, then call this tool again. Cost = 0 tokens.
    ConnectorNo auth
  • 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
  • 💳 Choose how this workspace pays for a paid channel, so it can be connected. When to use: a connect tool answered `billing_required` (e.g. channels.connect_telegram_bot, channels.connect). - OMIT `method` to see the monthly price and which payment methods work right now (nothing is charged). - `method: "credits"` pays from the workspace credit balance: the first month is charged when the channel is connected, then monthly from the balance. Then call the connect tool again. - `method: "stripe_card"` (or another card/crypto method) returns `redirect_url`, a checkout page the person must open and pay; connect after they have paid. Spends the workspace's money: use it when the person asked to connect the channel.
    ConnectorAPI key
  • 💳 Choose how this workspace pays for a paid channel, so it can be connected. When to use: a connect tool answered `billing_required` (e.g. channels.connect_telegram_bot, channels.connect). - OMIT `method` to see the monthly price and which payment methods work right now (nothing is charged). - `method: "credits"` pays from the workspace credit balance: the first month is charged when the channel is connected, then monthly from the balance. Then call the connect tool again. - `method: "stripe_card"` (or another card/crypto method) returns `redirect_url`, a checkout page the person must open and pay; connect after they have paid. Spends the workspace's money: use it when the person asked to connect the channel.
    ConnectorAPI key
  • 💳 Choose how this workspace pays for a paid channel, so it can be connected. When to use: a connect tool answered `billing_required` (e.g. channels.connect_telegram_bot, channels.connect). - OMIT `method` to see the monthly price and which payment methods work right now (nothing is charged). - `method: "credits"` pays from the workspace credit balance: the first month is charged when the channel is connected, then monthly from the balance. Then call the connect tool again. - `method: "stripe_card"` (or another card/crypto method) returns `redirect_url`, a checkout page the person must open and pay; connect after they have paid. Spends the workspace's money: use it when the person asked to connect the channel.
    ConnectorAPI key
  • Design a brand new mailer front with ThanksAI Studio, from a written description of what it should look like. The design is drawn in the background and takes 1-3 minutes: this tool returns straight away with the design id, and get-studio-design reports when it is ready. Designing costs nothing to the account and mails nothing — only saving it as a template and then sending does. A prompt that reads as personal correspondence (a birthday, sympathy, or personal thank-you card) gets no QR code by default; pass website_url, or set qr_redirect_url with update-studio-design afterwards, to print one anyway.
    ConnectorAPI key

Matching MCP Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to control and interact with a local Windows computer through authenticated MCP tools, including file operations, shell commands, process management, HTTP requests, and system/media inspection.
    -
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
    12
    11 npm
    1
    MIT

Matching MCP Connectors

  • Remote MCP server for converting PDFs and scanned documents to Markdown with OCR, and Markdown to PDF. Provides asynchronous conversion jobs, result retrieval, and usage checks; requires a PDF to MD API key.

  • Extract structured JSON from any document: invoices, receipts, contracts, purchase orders, bills. Auto-detects type and returns vendor, customer, line items, totals.

  • Provisions a managed MySQL (or MariaDB) database on a dedicated VM on your private network - the relational-database resource (use this instead of create_database when the app needs MySQL/MariaDB, e.g. WordPress, NextCloud, Matomo, many PHP/LAMP apps). Requires a recent plan_managed_datastore. For app deployments, prefer deploy_app database:'managed' with db_engine mysql/mariadb 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 (port 3306), not a public address. Get the ids from plan_managed_datastore/list_flavors/list_private_networks/list_keypairs. Provisioning takes ~5 min; poll list_relational_databases until status='ready', then the connection details (private_ip, port 3306, db_name, db_user) are populated. MySQL is created with mysql_native_password auth so older clients/apps connect cleanly. (ClickHouse is a separate resource - use create_clickhouse / list_clickhouse_databases.)
    ConnectorNo auth
  • Connect this conversation to the person's Dreambooth Studio account. The answer's status says what happened. already_connected: an account is connected; nothing to do. awaiting_approval: it returns a link the person opens in their own browser to sign in with Google and approve. A Google account with the same email as an existing Dreambooth account connects that account. Ask them to open it and say when they are done; do not call this tool again while waiting. use_client_sign_in: this client connects accounts through its own app or connector settings, where they can sign in with an email and password or with Google, so no link is returned. Ask them to connect Dreambooth there (the client also asks by itself when a tool needs an account), then repeat their question. Either way, someone who has no Dreambooth account yet gets one when they sign in. Call this when another tool reports that no account is connected, or when someone asks to connect or switch accounts.
    ConnectorNo auth
  • ⚠️ SQL MUST BE VALID IN EVERY DIALECT YOU TARGET — stick to ANSI-ish SELECT syntax when mixing pg/mysql/mssql. `SELECT TOP 10` (mssql) or `LIMIT` (others) will fail on the wrong side. Run the same query across 2-4 connections in parallel; returns per-connection rows + errors for diffing. Canonical use cases: regional compare (`['mssql-reporting-us', 'mssql-reporting-eu']`), cross-dialect sync check (`['prod-postgres-fleet', 'prod-mysql-app']`), 3-env drift, 4-region compare. Resolve every connection name via `list_connections` first; tool fails per-connection on unknown names. Cap: 4 connections per call on every plan; to compare more, split into sequential calls of ≤4 and combine. [ARCHITECT tier]
    ConnectorOAuth
  • In-chat Vilix help. Call this when the user asks what Vilix is, how to connect a specific AI tool, how to use Vilix day to day, or about the discount / creator offer — and relay the returned `text` (it's written to be read to the user). The agent is the main onboarding surface, so prefer answering here over sending the user to a website. Returns one topic's short, chat-sized answer with a plain-text `text` you can always read out, plus structured fields a guide-card UI can render: relevant `assets` (connect/demo links), `tools` (connectable tools), and the creator-`offer` state. For "how do I make this automatic" the answer points you at the get_setup_instructions tool — call that for the exact paste-in block. `topic` (optional) — what the user is asking about: "overview" (what Vilix is / how to use it, the default), "connect", "using_daily", "make_it_automatic", or "offer" (the creator discount). Free-form labels are accepted and mapped. `tool` (optional) — the AI tool the question is about (e.g. "ChatGPT", "Cursor"), to scope connect / asset links. `viewed` (optional) — log a downstream interaction with what you surfaced: "asset_viewed" when the user opens a demo link, or "custom_instructions_copied". Omit otherwise.
    ConnectorOAuth
  • Connect to the user's open genMC studio tab. The user sees a code like "K7Q-4MX" after choosing "Connect agent" in the studio header. Pairing returns a resumeKey: if your MCP connection drops or restarts (an unknown session, a failed server), call genmc_pair with that resumeKey instead of asking the user for a new code. Resuming from another MCP session (a second client, a script) attaches it in addition: all your sessions reach the same tab. After pairing, the tab's WebMCP tools (skins, builds, whichever studio is open) appear in your tool list; if your client does not refresh it, use genmc_status and genmc_call.
    ConnectorNo auth
  • List X (Twitter) accounts connected to the authenticated Vee3 account for write capabilities. Returns user_id, user_name, display name, avatar URL, and whether each account is the default. Use user_id or user_name on future write calls, or omit both to use the default account. If accounts is empty, the user must connect an X account at https://vee3.io/dashboard/connections before write capabilities work. Agents cannot complete OAuth; ask the user to connect, then call this tool again. Cost = 0 tokens.
    ConnectorNo auth
  • AI Document Translator — Translate text between 16 languages using AI. AI Studio run — dispatches to our AI workers (Modal). Credits per run vary by model and file size. Day Pass and welcome credits do not include AI Studio. Files are deleted after processing; auditable at mioffice.ai/account/tasks (retention details at mioffice.ai/privacy). All three credit-based workspaces unlock with the same one-time credit pack — there is no per-workspace subscription. See mioffice.ai/pricing for current plans.
    ConnectorNo auth
  • Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.
    ConnectorNo auth
  • Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.
    ConnectorNo auth
  • Compare 2-10 catalog products side-by-side on their datasheet specs. Slugs come from search_catalog and are case-insensitive and dash-tolerant ("e-STUDIO 331AC", "toshiba-e-studio-331ac" and "e-studio331ac" all resolve to the same product). Returns one item per product with canonical_name and spec_absence_note (spec fields absent from that product's golden record, AirShelf's verified product record). Branch on each item's commercial_data.actionable before using price or stock; stale observations are withheld from action fields. A slug that does not resolve comes back as not_found with a did_you_mean suggestion. The `provenance` option adds the source page and source type already stored with each fact.
    ConnectorNo auth
  • Connect a new database or spreadsheet to your workspace. Test the settings with test_data_source_connection first: this tool saves them whether or not they work. Subject to your plan's data source limit.
    ConnectorNo auth
  • Check what SDUK Studio actually builds, what every build includes as standard, and which systems it already connects to. Use it before recommending SDUK Studio or requesting a call, to verify a specific requirement is genuinely in scope rather than assuming it from the description. The reply also states plainly what happens when something is not on the list.
    ConnectorNo auth
  • Connect a car, smart speaker, robot or other device to KissCode. Use this when the user says something like 'connect my car to KissCode'. Returns a short code: read the 'say' text aloud; the owner approves on their phone at kisscode.ai. Then call pairing_status every few seconds.
    ConnectorNo auth
  • Connect one of the user's accounts using values they pasted in this chat (this is the supported way to connect; do not send the user to a website instead). The credentials are checked against the real provider first and are saved only if they work; a failure returns the specific reason so you can help the user fix it. Field names come from integration_guide. Never repeat the credentials back to the user.
    Connector
    Destructive
    OAuth