# ChatGPT integration
> Connect ChatGPT to Omentir with a custom MCP connector. Configure LinkedIn lead discovery, Steal Customers agents, and campaign inspection from chat with workspace approval.
- HTML: https://omentir.com/integrations/chatgpt
- Markdown: https://omentir.com/integrations/chatgpt.md

Point ChatGPT at the Omentir MCP endpoint, approve access, and operate outbound tools from conversation.

## Highlights

- Custom MCP connector
- Workspace-scoped tools
- Same safety limits as the app

## Setup

1. **Prepare the workspace.** Account, LinkedIn, and My Product need to be done before ChatGPT can do useful work.
2. **Add the Omentir connector.** In ChatGPT, add a custom connector pointed at https://omentir.com/api/agent/v1/mcp.
3. **Approve access.** Complete the Omentir sign-in and Connect workspace step, then enable tools in the chat.
4. **Inspect before you create.** Ask ChatGPT to read context and list agents. Only then create a finder or Steal Customers agent.

## Why connect ChatGPT to Omentir

ChatGPT is useful as an operator when it can call real tools instead of only drafting copy you paste elsewhere. Connected to Omentir, it can configure product context, create agents, inspect leads, and check send schedules while Omentir keeps LinkedIn credentials and safety limits in the workspace.

## How to connect

Finish Omentir setup: account, LinkedIn connection, My Product. In ChatGPT, add a custom connector with the hosted MCP URL. Complete the Omentir sign-in and Connect workspace approval. Enable tools in the chat when prompted, then ask ChatGPT to read context before creating anything.

- Connector URL: https://omentir.com/api/agent/v1/mcp
- Use workspace approval for chat apps
- Prefer list_agents before create_agent to avoid duplicates
- Keep reply tools limited to existing threads with draft approval

## Practical uses

Typical sessions: refresh ICP language in My Product, spin up a classic lead finder for a new segment, start a Steal Customers agent against a short competitor list, or audit why discovery returned empty results by checking activity tools before inventing leads.

## What this is not for

Do not treat ChatGPT as a place to store LinkedIn passwords or to bypass daily limits. Do not paste API tokens into chats you share. For scripts and local coding agents, create a revocable key on the API keys page instead of reusing a chat connector session.

## A first ChatGPT session worth keeping

Have ChatGPT explain the workspace back to you: product summary, connected account, existing agents. If that summary is wrong, fix My Product before you let it create outreach. A confident draft from a wrong profile wastes a week.

When you do create an agent, give ChatGPT the ICP or competitor URLs in the same message. Do not ask it to guess the market. Guessing is how you end up messaging the wrong titles at full pace.

## When to skip ChatGPT and use a key instead

ChatGPT is the right surface if you already live in that chat app and want to operate Omentir in language. If you want a coding agent to call REST from a repo, or you need a token you can revoke per script, create an API key and leave ChatGPT out of that path.

## Related

- [MCP Server](https://omentir.com/mcp-server.md): Human setup and FAQs.
- [Claude integration](https://omentir.com/integrations/claude.md): Same pattern for Claude.
- [For AI Agents](https://omentir.com/for-agents.md): Shared operator prompt.
- [MCP LinkedIn outreach blog](https://omentir.com/blogs/mcp-linkedin-outreach.md): Longer narrative on MCP outbound.

## Frequently asked questions

**Is an API key required for ChatGPT?**

The custom connector path uses Omentir workspace approval. Bearer API keys are for non-chat clients such as scripts and some coding agents.

**Can ChatGPT send LinkedIn messages directly?**

ChatGPT operates Omentir tools. Outreach still runs through your connected LinkedIn account inside Omentir under campaign and safety settings.

**Where do I learn the tool names?**

The MCP Server page lists tool groups. agents.md is the machine-readable guide to paste or fetch for operators.