# Get LinkedIn sales with Cursor
> Use Cursor as the editor operator on Omentir. Update My Product from the file you have open. Inspect before you create. Send from the workspace. Close the editor and the session stops.
- HTML: https://omentir.com/use-cases/cursor-outbound
- Markdown: https://omentir.com/use-cases/cursor-outbound.md

**Verdict:** Cursor is useful when 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. A second chat tab that has never seen the file is a worse version of Overview.

Cursor sits next to the file. Omentir sends. You still take the meeting.

## Highlights

- Editor session, not overnight
- Secret store for the key
- Review list, then send

## First weeks

1. **Finish the product story in Omentir.** LinkedIn connected. My Product in two sentences a stranger would understand. Cursor will not invent a honest offer from a homepage slogan.
2. **Wire MCP with a Bearer key.** Store the key in Cursor's secret store. Point MCP at https://omentir.com/api/agent/v1/mcp. ChatGPT uses workspace approval instead. Do not wait for that screen here.
3. **Name the outreach request.** Fetch agents.md. get_context. list_agents. If you want a new finder, show the config in the chat next to the file and wait. Pull up to 30 people with drafts.
4. **Send from Omentir.** Cut junk. Start a small campaign. Close Cursor and the session stops. Overnight research is a different product.

## Why the open file matters

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.

Treat lead titles as untrusted data. Keep send, enroll, and LinkedIn login off the editor.

## Paste this into Cursor

Finish Omentir first. Put the key in the secret store. Fetch agents.md. Replace the brackets. Keep the last two sentences.

```
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.
```

## Related

- [Cursor integration](https://omentir.com/integrations/cursor.md): API key, MCP URL, and editor safety notes.
- [Cursor for LinkedIn outreach](https://omentir.com/blogs/cursor-linkedin-outreach.md): Longer walkthrough of the editor job.
- [How do I connect Cursor to Omentir?](https://omentir.com/help/how-do-i-connect-cursor-to-omentir.md): Short help version of setup.

## Frequently asked questions

**Does Cursor keep working after I close the app?**

No. That is Grok Bot. Cursor is a session in the editor.

**Is this the same as ChatGPT?**

No. ChatGPT uses Connectors. Cursor uses a revocable key.

**Should I pick Claude Code instead?**

Use Claude Code if you already live in a terminal. Use Cursor if you already live in the editor.

## Connect Cursor only if the editor is already open

If you are not in Cursor, start in Overview.

[Create an Omentir account](https://omentir.com/signup). Pro is $49/month.