# Grok integration
> Connect Grok to Omentir with a custom MCP connector. Approve workspace access, then create lead finders or Steal Customers agents and inspect LinkedIn leads from chat.
- HTML: https://omentir.com/integrations/grok
- Markdown: https://omentir.com/integrations/grok.md

Add the Omentir MCP connector in Grok, approve access, and operate outbound tools from conversation.

## Highlights

- Custom MCP connector
- Same tool map as other chat apps
- Workspace approval

## Setup

1. **Prepare Omentir.** Connect LinkedIn and complete My Product so Grok has a real offer to work from.
2. **Add the custom connector.** In Grok, add a connector with https://omentir.com/api/agent/v1/mcp.
3. **Approve Connect workspace.** Sign in to Omentir when prompted and allow the workspace. Enable tools in the conversation.
4. **Start with read tools.** Ask Grok for context and stats, then list agents, before you let it create a finder.

## What Grok can do with Omentir

Connected through MCP, Grok can call Omentir tools for workspace context, My Product, classic lead finders, Steal Customers agents, lead inspection, activity, scheduled sends, and approved work on existing conversations. LinkedIn credentials stay inside Omentir.

This is the same hosted MCP surface Claude and ChatGPT use for chat-style connectors, with workspace approval instead of pasting a long-lived token into the chat transcript.

## Setup path

Finish Omentir basics: account, LinkedIn connection, My Product. In Grok, add a custom connector with the Omentir MCP URL. Sign in on Omentir and approve Connect workspace. Enable tools in the conversation if prompted.

- MCP URL: https://omentir.com/api/agent/v1/mcp
- No API key required for the chat connector path
- List agents before create_agent to avoid duplicates
- Optional operator prompt from /for-agents as the first message

## Good first session

Ask Grok to run get_context and get_stats, confirm readiness, then propose a single agent configuration for your approval. Prefer one clear segment over a broad autonomous expansion of titles and geographies.

## Limits

Daily send limits and campaign rules still apply. Grok is an operator interface, not a bypass around safety settings. You remain responsible for what gets sent from your LinkedIn account.

## A first Grok session that does not invent targeting

Give Grok the same written ICP you would give a teammate. If you only say 'find me SaaS founders,' you will get a wide, noisy list. If you name the role, the company size, and the trigger, the agent it creates will be easier to review.

Have Grok show the agent configuration before you leave it running. Confirm send windows and daily limits in the dashboard after. Chat operators are fast. The LinkedIn account still pays for a sloppy config.

## When another client is a better fit

If your team already standardized on Claude or ChatGPT, do not add Grok just to have another connector. One operator you actually watch is better than three you forget. Use Grok when that is already the chat app where the work happens.

## Related

- [MCP Server](https://omentir.com/mcp-server.md): Human setup and tool groups.
- [Claude integration](https://omentir.com/integrations/claude.md): Same connector pattern on Claude.
- [For AI Agents](https://omentir.com/for-agents.md): Shared operator prompt.

## Frequently asked questions

**Is Grok support the same as Claude?**

Chat apps share the custom MCP connector pattern. UI labels differ by product. The Omentir endpoint and workspace approval model are the same idea.

**Can Grok create Steal Customers agents?**

Yes, after My Product is complete and LinkedIn is connected, using competitor LinkedIn URLs and optional founder or employee profiles.

**Where is the full tool list?**

See /mcp-server for humans and /agents.md for machine-readable guidance.