Connections

icu.connectionsPublished by connections.icuOfficial publisherv1.0.0Updated Oct 24, 2026

Post deals, host events, import contacts and keep notes and memory across every assistant.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant post deals, host events, import contacts, and keep notes and memory shared across assistants.

What you can do
Post deals to the service from within a conversation. Create and host events. Import contacts into the account. Save and recall notes and memory that persist across different assistants.
When to use it
Useful when you want one assistant to publish deals or events, bring in a contact list, or keep notes and memory that carry over between assistants rather than staying in a single chat.
Requirements
A remote endpoint reached over streamable HTTP at the provider's hosted address. OAuth authentication is required, so a provider account and sign-in are needed. No environment variables or headers are declared.
Before you install
Sign-in is via OAuth to a third-party hosted service, so the provider holds your account data. The tools write data — posting deals, creating events, importing contacts and storing notes and memory — and imported contacts and saved memory are sent to and kept by that service.

Installation

In SourceWeft

  1. Open Connections 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/icu.connections%2Fconnections/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": {
    "connections": {
      "type": "http",
      "url": "https://studio.connections.icu/v1/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.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.

Other Connections integrations