Klipy

ai.klipyPublished by klipy.aiOfficial publisherv1.3.1Updated Oct 26, 2026

AI CRO for Agencies and MSPs: full automatic CRM; multichannel tracking; draft follow-ups.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Klipy is a remote MCP endpoint for an AI CRO aimed at agencies and MSPs, offering an automatic CRM, multichannel tracking and drafted follow-ups.

What you can do
  • Manage CRM records automatically for an agency or MSP sales pipeline.
  • Track customer interactions across multiple channels.
  • Draft follow-up messages for the assistant to review or send.
  • No individual tools are documented, so exact operations are not described in the listing.
When to use it
Consider it when an agency or managed service provider wants an assistant to keep CRM data current, follow activity across channels, and prepare follow-up drafts without manual data entry.
Requirements
A remote MCP endpoint at api.klipy.ai over streamable HTTP. OAuth authentication is required, so a Klipy account with an authorized connection is needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Klipy CRM data, which likely includes customer and contact records. Follow-up drafting and automatic CRM updates may write or send data; confirm what is created or sent before enabling it. Data is handled by the third-party Klipy service.

Installation

In SourceWeft

  1. Open Klipy 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.klipy%2Fklipy/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": {
    "klipy": {
      "type": "http",
      "url": "https://api.klipy.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.3.1LatestSep 18, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.