"How to update an MCP configuration file" matching MCP tools:

• remove_backgroundA

  OpenClipA

  Remove the background from an already-uploaded image `file` (a hashid from create_upload), returning a transparent PNG. This is FREE and only needs an account, no subscription. To use a local file: call create_upload, PUT the bytes to the returned upload_url, then pass that `id` here as `file`. Do NOT call complete_upload (that starts the paid clip pipeline); this free tool reads the uploaded file directly. Processing is ASYNCHRONOUS: this returns a `tool_job` hashid and `status: "queued"`. Poll get_tool_job_status with that `tool_job` until it reports `completed`, then it returns the downloadable PNG URL. Free usage is rate-limited per day with a per-file size cap; a clear error explains how to lift a limit.

  ConnectorOAuth

• update_monitorA

  LoadsterA

  Replace an existing Monitor's exposed configuration: name, Script, frequency, engine ids, failure and recovery thresholds, tags, and the acceptable-metric thresholds. An omitted threshold is cleared and omitted tags are removed, so read the current configuration with get_monitor first and send everything that should remain. Everything outside those fields is untouched: an update never changes whether the Monitor is enabled, and never touches its notification policies or maintenance windows, so a config edit cannot stop a running Monitor, start a stopped one, or unhook the user's alerting.

  Connector

  Destructive

  OAuth

• set_policiesA

  Veto — SQL Safety & Cost OracleA

  Replace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set.

  ConnectorNo auth

• update_webhookA

  MailercloudB

  Update an existing webhook's configuration. Only the fields given (name, url, events) are changed: the tool reads the webhook first and resends its current values for the rest, since the API needs all three. events replaces the current set. Use toggle_webhook to enable or disable. Set dry_run: true to see the merged values that would be sent.

  Connector

  Destructive

  API key

• fileshare_manageA

  Fast.ioA

  Fastio File Shares (write): create a durable share link bound to one workspace file (immutable binding), update, delete, and add/revoke per-user grants (grant-by-email creates a pending invite for an unregistered address). Destructive: delete (removes the share, not the file), grant-revoke. Reads are on `fileshare`. action='describe' gives the full action/param reference.

  Connector

  Destructive

  No auth

• retrieve_api_keyA

  Porkbun (official)A

  Collect the API key the user approved after `request_api_key`. Returns the public key (`apikey`, pk1_...) and the secret key (`secretapikey`, sk1_...) exactly once; store them securely right away (for example as PORKBUN_API_KEY / PORKBUN_SECRET_API_KEY in the MCP server's config, never in a committed file). Until the user approves, the answer says the request is still pending: wait and try again. This server keeps using the credentials it was started with; to switch to the new key, update its configuration and restart or reconnect it.

  ConnectorOAuth

• Compoid_update_recordA

  Compoid MCPA

  Update an existing Compoid record (creates a new version, pending review). Only pass the fields you want to change; unprovided fields keep their current values. An update with no changed fields is rejected as a no-op. Required: work_id: the record to update - a published record PID (e.g. '4171t-rc787'), a full record URL, or its OAI. Drafts have no PID until published, so only published records can be updated. Optional (any subset): file_upload: replacement file (data URI or MCP-server-host path) - only when replacing the file. title, description, creators, keywords, references: metadata to change. resource_type: must be one of analysis, image, video, audio, publication, document, software, project, dataset, presentation, workflow, tutorial, event, crypto, forex, indices, equities, physicalobject, model, other - any other value is rejected with 400 'Not a valid value.' subjects: up to 5 subject display names (https://www.compoid.com/subjects). Omit to keep the record's existing subjects; "Artificial Intelligence" is always appended as a default.

  ConnectorNo auth

• delivery_configureA

  Agents by MyInfluence AIA

  Set or update where and how this brand’s daily content package is delivered. Returns the signing secret ONCE, on first configuration or when rotate_secret is true — store it, it cannot be read back. telegram_enabled is FALSE by default: an agent-provisioned brand is webhook-only unless you deliberately turn the Telegram approval card back on, in which case BOTH fire.

  ConnectorAPI key

• get_wiki_attachmentA

  KaikuA

  Read one file attached to a wiki page — its bytes, base64-encoded — identifying the page by 'pageId' or by 'spaceKey' + 'title' and the file by 'filename' as get_wiki_page lists it. This is how a file is copied from one page to another: read it here, write it with add_wiki_attachment. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; for anything larger — or for putting the file on disk — the pm-files MCP server saves it to a path instead (local_files_setup says how to connect it). Reading needs only permission to see the page.

  ConnectorNo auth

• klyo_upload_packageA

  klyo games: publish HTML5 browser gamesA

  The way to release a game from a file on disk, with no tunnel and without exposing an unreleased game publicly. Returns three things at once: (1) `paczki_w_poczekalni`: packages already on the account that have not become a game yet, each with its `upload_id`; (2) `bilet`: a token valid for one hour ONLY for sending files, which you put in the `Authorization: Bearer` header (it opens no tool; you do not have it in your configuration, which is why you get it here); (3) a recipe: if you have a shell (curl), send the file with the ticket in two HTTP requests; if you do not, ask the owner to upload the ZIP in the studio at https://dev.klyo.pl/ (it lands in the waiting room, nothing is published) and call this tool again: the package will appear in `paczki_w_poczekalni`. Pass the returned `upload_id` to klyo_publish_game or klyo_update_game instead of `zip_url`. Do not save the ticket in project files. Examples: • How do I send a ZIP from my disk to klyo? • Publish this game, the file is on my computer • The owner uploaded a package in the studio, which one should I publish? • I don't want to expose the game publicly, how do I upload the package?

  ConnectorOAuth

• update_published_templateA

  BernuviaA

  Sends an UPDATE of one of YOUR templates that is already PUBLISHED (approved) to human review, like the edit button of the website. The update waits parked and the live version stays visible and on sale exactly as it is until a person decides: if it is approved it replaces the live version, if it is rejected the live version simply stays. Send in `fixes` only the fields that change (same allowed values and limits as when publishing, all in the input schema); everything you do not send is kept from the live version. The licence and the cover image (bannerUrl) cannot be changed ([FIELD_NOT_EDITABLE]). A template with an EXCLUSIVE licence that has already been sold can never be updated ([EXCLUSIVE_SOLD]): the buyer keeps exactly the listing and the file they bought, and an update that was waiting when it sold is not applied. Updating also requires being able to sell, the same as publishing ([MEMBERSHIP_REQUIRED] otherwise). For a new deliverable, upload the ZIP with zip_upload_link and pass it in `file`: it only replaces the live ZIP if the update is approved, and without it the current ZIP is kept. `useDraft: true` takes the changes from the edit draft of THIS template. If an update is already waiting it answers [EDIT_PENDING]: wait for the decision, or repeat with `replacePending: true` to replace it. An update that changes nothing is refused ([NO_CHANGES]). A REJECTED template is fixed with resubmit_for_review instead ([NOT_APPROVED]), and one under review or being published answers [TEMPLATE_IN_PROGRESS]. DRY RUN: with `dryRun: true` it checks that the template is yours and published and which fields would change, without sending anything and without spending quota. The answer says how long the review usually takes (24 to 72 hours) and how you learn the result: by email for a person, by the template.reviewed webhook or my_templates (hasPendingChanges) for an agent account.

  ConnectorAPI key

• configure_serverA

  Cycle MCPA

  Change the host-level configuration of a Cycle server: its nickname, its tags (the labels containers target through constraints.node.tags), what it allows (pool: containers with no tags; services: environment service containers; overcommit: CPU shares beyond the hardware, by overcommit_multiple), its base volume size (the space reserved for images; grows only, never shrinks), whether it accepts SSH and SFTP connections (SFTP is required for container volumes with remote access), whether gateway services may run on it, and the shared file systems it exposes to containers. Shared file systems come in two kinds, each under an identifier: a shared DIRECTORY on the host, and a shared MOUNT that attaches an external file system (NFS, EFS, ...) with a type, mount options, and source. Containers mount an identifier via shared_file_systems on deploy_application or reconfigure_container; this tool is the server half only. Nickname, tags, and allow apply immediately in one update with no job; tags are a complete replacement set, allow merges the passed flags over the current ones. Cycle applies features and shared file systems as two separate jobs, each replacing that whole group: the tool reads the current values, lays the fields you pass over them, and submits the full result, so anything you don't pass keeps its value. Shared file system directories and mounts are added (or replace an existing identifier); remove drops identifiers. Mount type, options, and source go to the host's mount verbatim, and a source the host cannot reach fails that job. Reconfiguring does not restart the server. Always call with preview:true first: it returns the server's current tags, allow flags, features and shared file systems, the field-by-field change list, the containers across the hub whose placement constraints reference a tag being removed ('constrained_by'), and for every identifier being removed or replaced the containers that mount it ('mounted_by'). With nothing to change, preview is a read of the server's configuration. Confirm with the user, then call again without preview. Steps run the update (nickname, tags, allow) first, then features, then shared file systems, and stop at the first failure; read 'steps' rather than assuming all-or-nothing.

  Connector

  Destructive

  API key

• start_updateA

  StoreFastA

  Step 1 of publishing an update to the Microsoft Store: makes the update and returns an upload link for its .msix. Pass appId, the package version (four numbers like 1.4.0.0, higher than the live one; ask the person if you can't tell), and the .msix file name and exact size in bytes (ask the person if you don't know them; Windows shows the size in bytes in the file's Properties). Without a shell, as in ChatGPT: reply to the person with upload.page as a clickable markdown link, like "Upload the .msix here: [storefast.app upload page](https://storefast.app/upload/...)", ask them to tell you when the page says Done, then call finish_upload. A file attached to a message never reaches StoreFast, so send the link even when the person attached the .msix. With a shell, as in Codex or Claude Code: run upload.shell (or PUT each part to upload.urlTemplate), then call finish_upload. The link works for an hour. If it expires, or the app already has an update waiting for its package, call start_update with that releaseId for a fresh link. Nothing reaches Partner Center until submit_update. Uploading again into an update replaces what was uploaded to it, so only send the package that update is for.

  ConnectorAPI key

• create_file_sessionA

  SmartpressA

  Create a file session for uploading proof/artwork files. Returns a **fileSessionId**. Once it is joined to a configuration session, add_to_cart attaches its files without you passing the ID. **Two workflows:** - **File-first** (no product chosen yet): call with no arguments. A placeholder product is used. When the product is chosen, you MUST pass this fileSessionId to create_config_session (or call link_file_session): nothing joins them otherwise, and the configuration has no files. The real product is then reconciled automatically. - **Config-first** (configuration session already exists): pass productConfigSessionId (and ideally the productId). The file session is created and linked immediately, so add_to_cart needs only the configuration sessionId. Once joined, the link is persisted server-side, so later tools (add_to_cart) need only the configuration sessionId.

  ConnectorNo auth

• oruk_get_startedA

  oruk SpeechA

  Quickstart for the oruk Speech API and this MCP server: how to get an API key, per-client MCP configuration snippets, SDK install commands, and an optional routing rule the user can add to their agent instructions. No API key required. Use this when setting oruk up for the first time or when the user asks how oruk works.

  ConnectorNo auth

• explain_when_issuers_reportA

  Credit GPS — Canadian creditA

  Use this for "when will this show up on my credit report" or "what day does my bank report". Returns how the monthly reporting cadence works in Canada, how long a change takes to appear on a file, and why an Equifax file and a TransUnion file for the same person differ. This bundled reference has no verified per-issuer transmission calendar and returns no exact reporting day. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

  ConnectorNo auth

• update_proxyA

  HTML/CSS to Image APIA

  Replaces the complete proxy configuration. Omitted optional settings, including authentication, are cleared. Within authentication, an omitted password requires retain_password: true and an unchanged username. Returns configuration without passwords.

  Connector

  Destructive

  OAuth

• update_og_configA

  HTML/CSS to Image APIA

  Replaces an existing Open Graph image configuration and returns the saved configuration in item. Call get_og_config first to inspect settings that should be preserved; omitted optional settings are cleared or reset to defaults. Supply the complete configuration for the chosen config_type. Changes affect subsequent image requests using this configuration. After a plan downgrade, only disabling is accepted and other changes are ignored.

  Connector

  Destructive

  OAuth

• add_attachmentA

  KaikuA

  Attach a file to an issue: pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Attaching a filename the issue already has replaces that file rather than adding a second copy, so retrying this call cannot double it. A file on the person's own disk — a screenshot, a PDF — is better attached by path through the pm-files MCP server than typed out as base64; local_files_setup says how to connect it. Returns the attachment's download URL. Requires permission to edit issues in that project.

  Connector

  Destructive

  No auth

• get_reminderA

  ReminderItA

  Get the full configuration of one reminder as JSON. Use when you need detail that list_reminders omits — the exact spoken message, cron expression, skip dates, channel toggles, or voice override. Also use this to read current values before a partial update, so you don't overwrite settings. Args: reminder_id: Reminder ID from list_reminders.

  ConnectorNo auth

• fetchA

  Pinto NotesA

  Reads a note, an app file, an app's data.json or a file, with line numbers (cat -n). Long text is read in parts: offset is the first line, limit how many (default 2000). A folder reads as its listing. Files: text files (TXT, CSV, JSON, code) as text you can edit; PDFs, Word, Excel and PowerPoint as their text; pictures as images. raw: true returns the file itself (base64, up to 10 MB).

  ConnectorOAuth