haggl.ai for merchants

ai.hagglPublished by haggl.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Run your haggl.ai sales agent from your assistant: budget, max discount, results. Sign-in required.

The publisher's own server: haggl.ai

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant run a haggl.ai sales agent, setting its budget and maximum discount and retrieving results.

What you can do
Connect an assistant to a haggl.ai sales agent and operate it from the conversation. Set the agent's budget and maximum discount. Retrieve the results of the agent's work. Sign-in through haggl.ai is required before use.
When to use it
Useful when you already use haggl.ai for sales negotiations and want to start or steer the agent, and check its outcomes, without leaving your assistant.
Requirements
A remote streamable HTTP endpoint at haggl.ai with OAuth sign-in required. No packages, environment variables or headers are declared, so a haggl.ai account is needed.
Before you install
The server can set a budget and a maximum discount on a live sales agent, which may affect real pricing or spending; review those values before running it. Access is tied to your haggl.ai account through OAuth.

Installation

In SourceWeft

  1. Open haggl.ai for merchants 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/ai.haggl%2Fmerchant/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": {
    "haggl-ai-for-merchants": {
      "type": "http",
      "url": "https://www.haggl.ai/api/mcp/merchant"
    }
  }
}

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 16, 2026

Score

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

    Publish an icon in the registry entry.

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

Other Haggl integrations