Claude integration

After Claude is connected to the Omentir MCP server, it can use Omentir tools to read workspace readiness, update My Product, create classic lead finders or Steal Customers agents, list leads with engagement context, check activity and the planned send schedule, and work with existing conversations under draft approval rules.

Claude does not receive your LinkedIn password. It operates through Omentir's workspace tools, with the same daily safety limits and campaign rules as the dashboard.

Create an Omentir account, connect LinkedIn, and complete My Product. In Claude, open Settings, go to Connectors, and add a custom connector with the Omentir MCP URL. Sign in on Omentir when prompted and approve Connect workspace. Enable Omentir tools in the conversation if Claude asks.

• MCP URL: https://omentir.com/api/agent/v1/mcp
• No API key required for the chat connector path
• Approve workspace access on Omentir before tools work
• Optional: paste the operator prompt from /for-agents as the first message

Ask Claude to run get_context and get_stats, confirm My Product is complete, list existing agents before creating new ones, and only create a lead finder or Steal Customers agent after you explicitly approve the targeting. Never ask it to broaden ICP silently or reply to threads without showing you the draft.

You remain responsible for LinkedIn rules, the accounts you connect, and the offers you send. Claude is an operator interface. Omentir enforces product limits; it does not replace your judgment about who to contact or what to claim.

Start with a question Claude can answer from tools: is My Product complete, how many agents exist, what is scheduled to send. Then give it one job, such as creating a lead finder for a written ICP, and make it show the targeting before it saves.

Do not ask Claude to invent a broader market or to reply to threads without showing the draft. The connector is powerful because it can change a real workspace. Treat it like a teammate with admin access, not like a chatbot that only talks.

If you need scripts, CI, or a coding agent in the repo, use an API key with Cursor, Claude Code, or REST. Claude's connector path is for conversational operation. It is a poor fit if you want headless jobs or if you are not willing to approve what it creates.