Supp

support.suppPublished by supp.supportOfficial publisherv1.0.3Updated Oct 24, 2026

Support you can control from anywhere, for less. 15+ integrations. Solve tickets easily

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work with customer support tickets through a hosted endpoint that advertises 15+ integrations.

What you can do
Supp is a remote MCP server for support work. Its description says it lets you control support from anywhere for less, offers 15+ integrations, and helps solve tickets easily. No individual tools are listed in the manifest, so the exact operations an assistant can perform are not documented here.
When to use it
Consider it when you want an assistant to help handle customer support tickets and your existing helpdesk or CRM is among the advertised integrations. Because the tool list is not published, confirm the available actions before relying on it in a live support queue.
Requirements
A remote MCP endpoint at over streamable HTTP. No packages, environment variables, or headers are declared, and the manifest declares no authentication. A network connection to the endpoint is required.
Before you install
The registry description gives no detail on what data the server reads or changes, so it is unclear whether it can write, reply to, or close tickets. The manifest declares no authentication, environment variables, or headers, but that does not guarantee the endpoint is open; check the provider's own terms before connecting an assistant to live support data.

Installation

In SourceWeft

  1. Open Supp in the dashboard and add it to a workspace.
  2. 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/support.supp%2Fmcp-server/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.

{
  "mcpServers": {
    "supp": {
      "type": "http",
      "url": "https://mcp.supp.support/"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.