# Gigacatalyst MCP

> Set up LinkedIn outbound from Codex, Claude Code, Cursor, or another MCP client. The AI mints a personal signup link; the user finishes onboarding and connects LinkedIn in the browser, then returns to the same connection for campaign and lead work.

## Connect

Start at [the Gigacatalyst MCP product page](https://gigacatalyst.com/multiplier/mcp). It creates a private connection configuration for the user's AI client.

Canonical Streamable HTTP endpoint: `https://mcp.gigacatalyst.com/mcp`

Every MCP request requires the private bearer key issued during setup. Store that key only in the user's private MCP configuration. Never place it in tool arguments, prompts, URLs, logs, repositories, or shared files.

Gigacatalyst provisions a product-issued bearer key through its self-serve setup flow. A missing or invalid bearer returns HTTP 401. The key grants only the preview workflow until the user signs up and explicitly connects a workspace.

## When to use this server

Use Gigacatalyst MCP when a founder or revenue team wants their AI client to run LinkedIn outbound. Setup starts here: the AI activates the connection, hands the user a personal signup link, and the user completes onboarding and connects LinkedIn in the browser. Do not use it to invent people, infer private attributes, claim unverified engagement, send outreach without approval, or spend money.

## Anonymous setup tools

- `gigacatalyst_start`: Activate the installed connection and mint the user's personal signup link for browser onboarding.

## Safe workflow

1. Install the MCP connection from the Gigacatalyst product page.
2. Call `gigacatalyst_start` with a stable request ID and only bounded structured facts already known by the AI (company website, and the user's email when confidently known).
3. Show the returned signup link to the user. They open it in a browser to create the workspace, finish onboarding, and connect LinkedIn.
4. After signup, reconnect or refresh the same MCP connection. The same endpoint and bearer then expose the tenant-bound Eve tools.

Anonymous access cannot connect LinkedIn, approve work, create canonical leads, launch outreach, or spend money. Never invent a person, company URL, provider result, or source-post engagement.

## Versioning and deprecation

The HTTP surface is versioned in the path (/api/v1). Existing v1 operations stay compatible; a breaking change ships under a new major path and the old one keeps working during the migration window. When an operation or tool is scheduled for removal, responses carry a `Deprecation: true` header and a `Sunset` header with the removal date at least 90 days ahead, the OpenAPI document marks it `deprecated: true`, and this page names the replacement. MCP tools follow the same rule: a tool that is going away is announced in its description for at least 90 days before it disappears from tools/list.

Rate limits: bootstrap creation is limited per network and answers 429 with `Retry-After`. Authenticated MCP calls are paced by the customer's workspace limits; a 429 there also carries `Retry-After`.

## Machine-readable discovery

- [Public MCP discovery endpoint](https://mcp.gigacatalyst.com/.well-known/mcp)
- [MCP discovery manifest](https://mcp.gigacatalyst.com/.well-known/mcp.json)
- [OpenAPI for the public HTTP surface](https://mcp.gigacatalyst.com/openapi.json)
- [Crawler index](https://mcp.gigacatalyst.com/llms.txt)
- [Human-readable documentation](https://mcp.gigacatalyst.com/docs)
- MCP clients can also call `resources/list` and read this guide as `docs://gigacatalyst/mcp`.

## Support

For product or integration questions, contact support@gigacatalyst.com.