Gigi AI

ai.usegigiPublished by usegigi.aiOfficial publisherv1.5.1Updated Oct 24, 2026

LinkedIn outreach from Claude with a human veto: review, approve and send drafts, triage replies.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Gigi AI lets an assistant run LinkedIn outreach from Claude, with a human veto: review, approve and send drafts, and triage replies.

What you can do
Review and approve drafted LinkedIn outreach messages before they are sent. Send approved drafts to contacts. Triage incoming replies.
When to use it
For people who want an assistant to prepare LinkedIn outreach and sort replies while keeping a human approval step before anything is sent. Suitable when you already use Claude and want the outreach workflow inside it. It is not for other channels or general messaging.},
Requirements
A remote endpoint reached over streamable HTTP with OAuth authentication required. No packages, environment variables or headers are declared.
Before you install
It can send messages on your behalf and act on replies, so review drafts before approving them. Access is granted through OAuth to your account; check what the authorization covers.

Installation

In SourceWeft

  1. Open Gigi AI 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.usegigi%2Fgigi/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": {
    "gigi-ai": {
      "type": "http",
      "url": "https://usegigi.ai/api/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

2
  1. v1.5.1LatestSep 18, 2026
  2. v1.5.0Sep 18, 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.