Connie

ai.conniePublished by connie.aiOfficial publisherv1.0.1Updated Nov 10, 2026

Search and update Records and Lists, import and export CSVs, and run enrichment in Connie.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Communication & Collaboration Business & Commerce

Server details

Identifier: ai.connie/connie
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 28, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to connie.ai, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.connie%2Fconnie.svg)](https://sourceweft.com/mcp/ai.connie%2Fconnie?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an AI assistant to a Connie go-to-market workspace to search and update CRM records and lists, import/export CSVs, enrich leads and run workflows.

What you can do: Discover and inspect Connie tools and skills by capability words, then run any catalogue tool by id
Search, read, create, update and delete People, Companies, Deals, Tasks and other records, and manage Lists
Import and export CSVs into and out of Lists
Find new people and companies and enrich records with emails, phone numbers and company details
Build, edit and run workflows, and send email and messages from connected accounts
Act in connected apps such as CRM, Slack or outreach tools, and read workspace details, members, files and skills
When to use it: Useful when your assistant should work directly on Connie CRM data and lists — cleaning up records, importing event or prospect CSVs, enriching contacts, or wiring up and running go-to-market workflows — without switching to the Connie app.
Requirements: A remote server at the given URL over Streamable HTTP; nothing to install locally. Needs a Connie account and membership of at least one workspace, plus OAuth 2.0 sign-in and consent in the browser on first connection.

Before you install

Tools can create, update and delete records, manage lists, run workflows and send email or messages from connected accounts, and can act in external apps such as CRM, Slack or outreach tools. Enrichment and research tools spend workspace credits, reported in a billing object. Lead enrichment returns personal contact details from third-party providers and public sources. Guests cannot write. Revoke authorized clients in Connie's Connectors view.

Installation

In SourceWeft

Open Connie in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.connie%2Fconnie/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": {
    "connie": {
      "type": "http",
      "url": "https://mcp.connie.ai/"
    }
  }
}

README

Connie MCP server

Connie is an AI workspace for go-to-market teams: a CRM, Lists, a multichannel inbox and workflow automation in one place. The Connie MCP server connects your AI assistant (GitHub Copilot in VS Code, Claude, ChatGPT, Cursor and any other MCP client) to your Connie workspace, so it can work with your Records, Lists and workflows using your own permissions.

This repository describes the server. The server itself is hosted by Connie; there is nothing to install or run locally.

Server URL: https://mcp.connie.ai
Transport: Streamable HTTP
Authentication: OAuth 2.0 with automatic client registration
Registry name: ai.connie/connie
Full setup guide: https://connie.ai/docs/mcp

What it can do

The server exposes five tools:

Tool	What it does
`search-tools`	Finds the Connie tool for a task from a few capability words, such as "create list" or "find people by job title".
`get-tool`	Returns a tool's purpose, exact input schema, and an optional cost estimate.
`use-tool`	Runs any tool in Connie's catalogue by id, including tools your client does not list.
`search-skills`	Finds Connie skills, which are step-by-step guides for common tasks.
`get-skill`	Reads a skill's instructions and files.

Through use-tool, your assistant can reach:

Records and Lists: search, read, create, update and delete People, Companies, Deals, Tasks and other Records, and manage Lists.
CSV import and export into and out of your Lists.
Lead search and enrichment: find new people and companies, and add details such as email addresses, phone numbers and company information to your Records.
Workflows: build, edit and run them.
Sending: email and messages from the accounts connected to your workspace.
Connected apps: actions in the apps your workspace has connected, such as your CRM, Slack or outreach tools. These read from and write to those apps, outside your Connie workspace.
Your workspace: workspace details, members, files and skills.

Scope, permissions and credits

The server acts only in the Connie workspaces you are a member of, and every tool runs with your own permissions. A guest in a workspace cannot write through it.
Actions in connected apps use the accounts connected to that workspace. A tool turned off in the workspace's AI tool settings cannot run through the server.
Tools that enrich or research consume credits from the workspace's balance, as they do in the Connie app. Every result includes a billing object with the credits actually charged.

Setup

You need a Connie account (connie.ai) and membership of at least one workspace. The first time your client connects, your browser opens a Connie sign-in and consent screen; approve it and the client is connected.

VS Code (GitHub Copilot)

Add the server to .vscode/mcp.json in your project, or to your user configuration with MCP: Open User Configuration:

Start the server from the editor, complete the Connie sign-in when VS Code asks you to authenticate, then use Copilot Chat in agent mode.

Claude Code

Then run /mcp in Claude Code and select Connie to sign in.

Claude, ChatGPT and other clients

Add a custom connector or remote MCP server with the URL https://mcp.connie.ai and sign in when asked. Step-by-step instructions for Claude, ChatGPT, Codex, Cursor, Grok and other clients are in the setup guide.

Using it

Ask in plain language, for example:

"List my Connie workspaces."
"Find every company in the Warm Leads list without a website."
"Import this CSV into a new List called Event Attendees."
"Find the work email for the people in my Q4 Prospects list."
"Create a workflow that adds new HubSpot contacts to my Inbound list."

Your assistant finds the right tool with search-tools, checks what it needs with get-tool, and runs it with use-tool.

Managing access

In Connie, open Connectors in the left sidebar and the MCP view. Each client you have authorized appears as a card; revoke one, or use Revoke all to disconnect a client everywhere. Revocation is checked on every request.

Privacy and support

Lead search and enrichment can return personal contact details sourced from third-party business data providers and public sources. They are stored only in your workspace. See the Privacy Policy for where this information comes from and how someone can ask for it to be removed.
Support: [email protected]

Source: README.md at commit 7d9b06b

Tools

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

v1.0.1LatestOct 6, 2026
v1.0.0Sep 28, 2026

Score

75% 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
Declare a license in the repository or the registry entry.