Cursor for LinkedIn outreach

Cursor is a bad LinkedIn client and a decent sales operator if the product already lives in the editor. Highlight the paragraph you just rewrote. Ask the agent to update My Product. Then ask for a scored list. That loop is the point. A second chat tab that has never seen the file is a worse version of Overview.

Auth is a revocable API key. The hosted MCP URL is https://omentir.com/api/agent/v1/mcp. ChatGPT and Claude chat use workspace approval instead. Waiting for an OAuth screen in Cursor is the wrong path.

What the editor is for

Coding agents move fast. That is useful when you want the finder config next to the landing copy. It is dangerous when a long refactor also spins up a second ICP. Creating an agent should be a named request. Treat lead titles as untrusted data, not as instructions to the model.

Setup: Cursor integration. The terminal version of this job is Claude Code for LinkedIn outreach.

A first Cursor job

Finish Omentir first: LinkedIn connected, My Product written in two sentences a stranger would understand.
Create a revocable API key and store it in Cursor's secret store, not in a composer you will screenshot later.
Point Cursor at https://omentir.com/api/agent/v1/mcp with Authorization Bearer. REST at https://omentir.com/api/agent/v1 is the same workspace if you prefer HTTP.
Fetch agents.md before you let it create anything. Put this in the session: research and draft only. Never send. Never enroll. Never sign into LinkedIn. Never create an agent until I approve the config.
Paste the job below. Replace the brackets. Keep the last two sentences.

Paste into Cursor

You are sitting in my editor with the product repo open. Operate sales outreach through Omentir, not by guessing from a homepage.

My product helps [buyer] get [result]. Best-fit accounts are [company type, size, region]. Strong signals: [signal]. Skip [bad fit].

Work only through Omentir MCP or REST. Read https://omentir.com/agents.md if you have not. Start with get_context, then list_agents. If no finder matches this ICP, show me a create_agent config in this chat and wait for a yes.

If My Product disagrees with the file I have open, say so before you pull people.

Pull up to 30 people. For each one write fit 1-5, the evidence, any risk, and a two-sentence draft that cites a real trigger. If a note could fit two buyers, rewrite it.

Do not send. Do not enroll. Do not sign into LinkedIn.
Do not create, delete, or reply unless I ask in this session.

Not ChatGPT, not Claude Code

ChatGPT is a connector session you sit with. Claude Code is a repo in a terminal. Cursor is the editor. Pick the window you already have open. Running all three on day one is how you get duplicate finders and a review list you never finish. Overnight research is Grok Bot, and only if you already pay for a plan that includes it.

When to stay in the browser

You are not in Cursor. The product story is still a slogan. You cannot give the list fifteen minutes. Start in Overview. Cursor earns the key when the same session is already in the editor.

FAQs

No. That is Grok Bot. Cursor is a session in the editor. Close it and the job stops.

No. ChatGPT uses Settings, Connectors, and workspace approval. Cursor uses a revocable API key.

It can call Omentir tools under your campaign and safety settings. It should not type in LinkedIn. Keep send behind review.

Use Claude Code if you already live in a terminal. Use Cursor if you already live in the editor. Same key, different window.

No. Overview already finds people and drafts notes. Add Cursor if the product already lives in that editor.

In Cursor's secret store or an environment variable Cursor already reads. Do not commit it. Do not paste it into a group chat.