SAGA

app.thesagaPublished by thesaga.appOfficial publisherv1.0.0Updated Oct 24, 2026

SAGA CRM for network marketing teams: contacts, pipelines, follow-ups and broadcasts over MCP.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

SAGA is a remote MCP server for a CRM built for network marketing teams, giving an assistant access to contacts, pipelines, follow-ups and broadcasts.

What you can do
  • Work with CRM contacts and pipelines for a network marketing team
  • Manage follow-ups and broadcasts through the assistant
  • The registry description names contacts, pipelines, follow-ups and broadcasts, but no individual tools are listed, so exact capabilities are not documented here.
When to use it
Worth considering if your team runs network marketing or referral-style sales in SAGA and you want an assistant to work with the same contacts, pipelines and follow-up activity from chat.
Requirements
A remote MCP endpoint at mcp.thesaga.app over streamable HTTP. OAuth authentication is required, so a SAGA account with access to the workspace is needed. No environment variables or headers are declared.
Before you install
The server is authenticated and acts on CRM records, so an assistant may read or change contacts, pipeline stages, follow-ups and broadcasts in your workspace. Grant only the access level you are comfortable with, and review any sending or editing actions before they run.

Installation

In SourceWeft

  1. Open SAGA 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/app.thesaga%2Fsaga/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": {
    "saga": {
      "type": "http",
      "url": "https://mcp.thesaga.app/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 15, 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.