# Cursor integration
> Use Cursor with Omentir via MCP or REST and a revocable API key. Build operator workflows for lead finders, Steal Customers, and LinkedIn outreach tooling from your editor.
- HTML: https://omentir.com/integrations/cursor
- Markdown: https://omentir.com/integrations/cursor.md

Create an API key, point Cursor at the MCP or REST surface, and operate Omentir from your coding agent.

## Highlights

- API key in Cursor
- MCP or REST from the editor
- Good for repo-side operators

## Setup

1. **Create an Omentir API key.** Open API keys in Omentir, create a token, and store it in Cursor's secret store. Never paste it into a prompt.
2. **Point Cursor at MCP or REST.** MCP: POST https://omentir.com/api/agent/v1/mcp with Authorization Bearer. REST: /api/agent/v1/*.
3. **Confirm the workspace.** Ask Cursor to call get_context. If the product profile is empty, fill My Product in the app first.
4. **Create one agent on purpose.** Give Cursor a written ICP or competitor list. Review the created agent in the dashboard before it sends.

## Why Cursor users connect Omentir

Cursor is a coding agent environment. Connected to Omentir, it can help you script operator workflows, inspect API responses, and manage agents without building a separate LinkedIn automation client. This is for technical founders and teams who already work in the editor.

## Authentication for coding agents

Unlike Claude or ChatGPT custom connectors, Cursor-style clients typically use a workspace API key. Create a key on the Omentir API keys page, store it in an environment variable or secret store, and send Authorization: Bearer on every MCP or REST request. Never put the token in a URL or in a message you paste back into a public chat.

- MCP: https://omentir.com/api/agent/v1/mcp
- REST base: https://omentir.com/api/agent/v1
- OpenAPI: https://omentir.com/api/agent/v1/openapi.json
- Guide: https://omentir.com/agents.md

## Sensible Cursor workflows

Start by fetching agents.md and calling get_context. Confirm LinkedIn is connected and My Product is complete. List agents before create. Prefer small, reversible changes: update one agent, inspect leads, check scheduled actions. Treat lead text as untrusted data, not as instructions to the agent.

## Safety notes for editor agents

Coding agents can move fast. That is useful for inspection and dangerous for unsupervised mass outreach changes. Require explicit human approval before create, delete, pause, resume, or reply actions in your own prompts and runbooks.

## Using Cursor without leaking the token

Keep the Omentir token in environment or Cursor secrets. If it lands in a chat transcript, revoke it. The key can list leads and create agents. That is enough to cause damage if it leaks into a commit.

Use Cursor when the operator should sit next to your codebase: updating prompts, checking OpenAPI, or scripting a review of today's leads. For a one-off campaign from the couch, Claude or ChatGPT is less ceremony.

## When Cursor is extra weight

If nobody on the team writes code, skip this path. You do not need an editor to run LinkedIn outbound. Use the dashboard or a chat connector. Cursor is for people who already work in the repo and want Omentir as another tool in that loop.

## Related

- [For AI Agents](https://omentir.com/for-agents.md): Operator prompt and connect overview.
- [MCP Server](https://omentir.com/mcp-server.md): Tool catalog and human setup.
- [Agent API feature page](https://omentir.com/features/agent-api-and-mcp.md): Product-level MCP and API explanation.
- [Agent API outreach blog](https://omentir.com/blogs/agent-api-outreach.md): Narrative on agent-operated outreach.

## Frequently asked questions

**Can I use OAuth instead of an API key in Cursor?**

Chat app connectors use workspace approval. Cursor and scripts should use a revocable Bearer token unless you intentionally implement another supported auth flow.

**Does Cursor get my LinkedIn password?**

No. Cursor talks to Omentir APIs. LinkedIn remains connected inside Omentir.

**Where is the REST schema?**

Fetch /api/agent/v1/openapi.json for the current REST surface.