Qualy

com.qualyhqPublished by qualyhq.comOfficial publisherv0.3.0Updated Nov 11, 2026

Connect your AI assistant to Qualy to manage payments, billing, and contacts.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Connects an AI assistant to Qualy to manage payments, billing, and contacts.

What you can do
Qualy is a remote MCP server that links an assistant to a Qualy account for payments, billing, and contact management. The manifest does not list individual tools, so the exact actions available are not documented here. Access is over a remote HTTP endpoint with OAuth sign-in or an API key.
When to use it
Worth considering when you already use Qualy for payments, billing, or contacts and want an assistant to work with that data directly. It is less useful if you do not have a Qualy account.
Requirements
A remote MCP connection to the Qualy endpoint. A Qualy account with OAuth sign-in, or a Qualy API key supplied as a bearer token in the Authorization header for headless use. Network access to the Qualy service.
Before you install
The server handles payments, billing, and contact data, so actions may move money or change customer records; confirm what each tool does before use. The Authorization header carries a secret API key for headless use, so keep it out of logs and shared configuration. Data is sent to the third-party Qualy service.

Installation

In SourceWeft

  1. Open Qualy 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/com.qualyhq%2Fqualy/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": {
    "qualy": {
      "type": "http",
      "url": "https://api.qualyhq.com/v1/mcp"
    }
  }
}

README

This repository has no README.

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

2
  1. v0.3.0LatestOct 4, 2026
  2. v0.1.0Sep 16, 2026

Score

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

    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.