Squish

co.squishPublished by squish.coOfficial publisherv1.0.0Updated Oct 29, 2026

Manage your Squish domains, DNS, hosting, backups and site files from your AI assistant.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFiles & Storage

Overview

AI-generated overview

Squish lets an AI assistant manage Squish domains, DNS records, hosting, backups and site files through a remote OAuth-protected endpoint.

What you can do
  • Manage domains and DNS records on a Squish account
  • Handle hosting settings for sites
  • Create and manage backups
  • Work with site files
  • All actions run against the Squish API through a remote endpoint
When to use it
Useful when you already host domains or sites with Squish and want to check or change DNS, hosting, backups or files from a chat instead of the dashboard.
Requirements
A remote MCP endpoint at api.squish.co with OAuth sign-in; no local package or environment variables are needed. A Squish account with domains or sites to manage is implied.
Before you install
The server can change domains, DNS, hosting, backups and site files, so mistakes can take sites offline or alter records. Access is granted through OAuth to your Squish account; review the scopes requested and confirm destructive actions before approving them.

Installation

In SourceWeft

  1. Open Squish in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.squish%2Fsquish/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "squish": {
      "type": "http",
      "url": "https://api.squish.co/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Squish integrations