Loops

io.github.loops-soPublished by GitHub account loops-sov1.0.0Updated Oct 24, 2026

Manage Loops contacts, mailing lists, campaigns, and transactional email from your Loops account.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage Loops contacts, mailing lists, campaigns, and transactional email.

What you can do
This server exposes a Loops account's email marketing features to an assistant. Per the description, the assistant can manage contacts, mailing lists, campaigns, and transactional email. No tool list is provided in the manifest, so the exact operations depend on the service's documentation.
When to use it
Use it when an assistant should work directly with contacts, mailing lists, campaigns, or transactional email in a Loops account instead of switching to the Loops interface.
Requirements
Needs network access to the remote endpoint at mcp.loops.so and OAuth authorization with a Loops account. No environment variables or headers are declared.
Before you install
The server manages campaigns and transactional email, so it may send messages and change contacts or lists, and it handles customer contact data. Check the OAuth scopes granted during authorization and watch for accidental sends or data changes.

Installation

In SourceWeft

  1. Open Loops 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/io.github.loops-so%2Floops/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": {
    "loops": {
      "type": "http",
      "url": "https://mcp.loops.so/"
    }
  }
}

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.0LatestSep 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.