Converly

io.converlyPublished by converly.ioOfficial publisherv1.0.0Updated Nov 2, 2026

Set up and manage conversion tracking by chatting with your AI assistant.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Hosted Converly connector that lets an assistant set up and manage website form conversion tracking and send conversions to ad platforms.

What you can do
  • Manage sites and tracking install: list sites, create a site, get the install snippet and check install status
  • Build and manage conversion flows: list, read, create, update, validate, publish, unpublish and delete flows
  • Manage ad destinations: list destination types and connected platforms, connect or disconnect a platform, check handoff status, list conversions
  • Inspect conversions and events: list events, view event details, send a test event
  • Discover trigger and action types for building flows
  • Review account and billing: read subscription, list plans, change plan; add internal traffic rules to exclude your own team
When to use it
Useful when you run a Converly account and want to set up or adjust form conversion tracking, connect Google Ads, Meta or GA4, publish flows, or diagnose why conversions are not showing up, without leaving the chat.
Requirements
A remote hosted server at app.converly.io added as a custom connector; nothing to install. OAuth login to a Converly account is required, and a new account starts a free trial. The AI client must support custom connectors, which may require a paid plan on the AI side.
Before you install
The assistant can create, update, publish and delete flows, disconnect ad platforms, and change your subscription plan; destructive and billing actions are said to require confirmation by name. Ad platform logins must be completed by you in the browser via a link the assistant provides. Connecting requires authorizing access to your Converly account, and changing plans may incur charges.

Installation

In SourceWeft

  1. Open Converly 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.converly%2Fconverly/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": {
    "converly": {
      "type": "http",
      "url": "https://app.converly.io/mcp"
    }
  }
}

README

Converly MCP

Set up and manage your conversion tracking by chatting with your AI assistant.

Converly tracks form conversions and fires them to ad platforms (Google Ads, Meta, GA4, and more) when someone submits a form on your website. The Converly MCP server lets an AI assistant like Claude or ChatGPT do that work for you: connect ad platforms, build and publish conversion flows, install tracking, and check your conversions, all inside your Converly account.

This is a remote, hosted MCP server. There is nothing to install or run. You add it as a custom connector in your AI assistant and authorize it, and that is it.

Connector address: https://app.converly.io/mcp

Use with Claude Code and Cowork (plugin)

This repository is also a Claude Code plugin. It bundles the hosted connector together with two skills, one for guided conversion-tracking setup and one for diagnosing missing conversions.

/plugin marketplace add converlyio/converly-mcp/plugin install converly@converly

The plugin connects to the same hosted server; you authorize with your Converly account on first use.

What you can do

Connect it, then just say what you want. For example:

  • "Connect my Google Ads account and set up conversion tracking for my contact form."
  • "Create a flow that sends a Lead event to Meta whenever someone submits my Typeform."
  • "Did my form conversions fire to Google Ads yesterday? Show me what happened."
  • "Why is my conversion not showing up in Google Ads?"
  • "Publish my new flow and give me the snippet to install on my site."
  • "Add our office IP so our own team visits do not get tracked."

Connect it

Claude (web or desktop)

  1. Open Settings, then Connectors, then Add custom connector.
  2. Paste the address: https://app.converly.io/mcp
  3. Authorize it. You log in to Converly (or create an account, which starts a free trial) and approve access.
  4. Start a new chat and try "Help me set up conversion tracking."

ChatGPT

  1. Enable Developer Mode under Settings, then Apps, then Advanced.
  2. Add a connector and paste the address: https://app.converly.io/mcp
  3. Authorize it, then start chatting.

Custom connectors require a supported plan on the AI side. Claude allows one custom connector on the Free plan and more on paid plans. ChatGPT requires a paid plan with Developer Mode.

How it stays safe

You stay in control the whole way:

  • You authorize the connection through Converly's own login and a consent screen.
  • The assistant cannot finish ad platform logins by itself. When you connect Google Ads or Meta, it hands you a secure link and you complete the login in your browser.
  • Anything destructive or billing related requires explicit confirmation. Deleting a flow, disconnecting a platform, or changing your plan all require you to confirm by name first.
  • Access is scoped, and every read or write is checked against your account on each request.

Tools

The server exposes 27 tools, grouped here by what they do:

Sites and install list_sites, create_site, get_install_snippet, get_install_status

Flows (a flow fires a conversion when a form is submitted) list_flows, get_flow, create_flow, update_flow, validate_flow, publish_flow, unpublish_flow, delete_flow

Destinations (your ad platforms) list_destinations, list_destination_types, connect_destination, check_handoff_status, disconnect_destination, list_conversions

Conversions and events list_events, get_event_detail, send_test_event

Discovery list_trigger_types, list_action_types

Account and billing get_subscription, list_plans, change_plan

Internal traffic add_internal_traffic_rule

The server also ships guided prompts (one-click workflows in clients that support them): set up conversion tracking, connect an ad platform, and check recent conversions.

Links

Security and data handling

Declared for reviewers and anyone auditing this plugin before installing it.

This plugin contains no executable code. It is a set of manifests plus two Markdown skill files. There are no install or lifecycle hooks, no bundled binaries or minified code, no postinstall steps, and nothing is downloaded or run at install time.

Network endpoints contacted:

  • https://app.converly.io/mcp — the hosted Converly MCP server, and the only endpoint this plugin causes an agent to call. It is declared in .mcp.json as a remote streamable HTTP server.

Credentials: none are stored in, read by, or bundled with this plugin. Access is authorized through OAuth against the user's own Converly account on first use, and the resulting token is held by the MCP client, not by anything in this repository. The plugin never reads local files, environment variables, SSH keys, or .env files.

Ad platform credentials never pass through this plugin or the MCP server. Connecting a destination such as Google Ads or Meta returns a Converly-hosted link that the user opens in their own browser to authorize the platform directly.

Scope: the MCP server exposes named, purpose-scoped tools. There is no shell-execution tool and no catch-all passthrough. Destructive operations (deleting a flow, disconnecting a platform, changing the plan) require explicit user confirmation, and tools carry read-only and destructive annotations so clients can prompt appropriately.

Telemetry: none beyond the API requests the user's own actions generate.

About this repository

This repository is the public home and documentation for the Converly MCP integration. It does not contain the server code. The server is a hosted part of Converly and runs at https://app.converly.io/mcp. For questions or issues with the MCP, open an issue here or contact Converly support.

Source: README.md at commit 15b8485

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

85% 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
  • License10 pts