You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Official LeadMagic plugin for Cursor: connect the editor to LeadMagic’s **hosted MCP** for credit-aware B2B enrichment—work emails, mobile, profile-to-email, job-change signals, account research, competitors, technographics, people-by-role, and credits.
3
+
Official LeadMagic plugin for Cursor. Connect Cursor to LeadMagic's hosted MCP for credit-aware B2B enrichment and GTM research: work email validation and discovery, mobile lookup, LinkedIn profile to work email, job-change signals, account research, competitors, technographics, people by role, and credit balance.
- A hosted LeadMagic MCP endpoint at `https://mcp.leadmagic.io/mcp`
10
+
- OAuth sign-in in Cursor by default
11
+
- 10 LeadMagic MCP tools for contact and account workflows
12
+
- Cursor-native packaging: rules, skills, commands, and a dedicated enrichment agent
13
+
- In-editor docs via `leadmagic://docs`
8
14
9
-
-**Default auth:****OAuth** in Cursor (browser sign-in). No API keys are stored in this repo’s `mcp.json`.
10
-
-**Optional API-key mode:** Use environment variable `LEADMAGIC_API_KEY` and the header pattern in [MCP configuration](#mcp-configuration). Never commit keys, tokens, or `.env` files—see [SECURITY.md](SECURITY.md) for reporting issues and hardening notes.
11
-
-**Data:** Tool calls send the inputs you or the agent provide (e.g. emails, names, company names or domains, profile URLs) to LeadMagic’s hosted service. Read [Privacy](https://leadmagic.io/privacy), [Terms](https://leadmagic.io/legal/terms), and [Support](https://leadmagic.io/docs/support).
15
+
This repository packages the Cursor plugin. It does not run a local MCP server. The MCP server is hosted by LeadMagic.
12
16
13
-
## What’s included
17
+
It follows Cursor's public plugin model documented at [https://cursor.com/docs/plugins](https://cursor.com/docs/plugins).
14
18
15
-
| Area | Details |
19
+
## Included in the plugin
20
+
21
+
| Area | Included |
16
22
| --- | --- |
17
-
|**MCP**| Hosted endpoint `https://mcp.leadmagic.io/mcp` (HTTP), **OAuth** by default |
**MCP vs REST:** For direct `https://api.leadmagic.io` integration, schemas, and smoke tests, use [LeadMagic OpenAPI](https://github.com/LeadMagic/leadmagic-openapi) and [product docs](https://leadmagic.io/docs). MCP tools cover a **subset** of the REST surface (e.g. jobs/ads are not MCP tools today).
31
+
Choose the path that fits how you want to use the plugin.
23
32
24
-
**Same plugin model as other Cursor plugins:**[Cursor Plugins](https://cursor.com/docs/plugins), [plugin-template](https://github.com/cursor/plugin-template). Similar bundle to [Encore’s Cursor plugin](https://github.com/encoredev/cursor-plugin) (rules, skills, MCP, agent, commands); LeadMagic uses **remote HTTP MCP** instead of a local stdio server.
33
+
### Option 1: Team marketplace import
34
+
35
+
In Cursor, go to `Dashboard -> Settings -> Plugins -> Team Marketplaces -> Import` and use:
Reload Cursor (`Developer: Reload Window`), complete **OAuth** when the LeadMagic MCP server connects, then try: *“Check my LeadMagic credit balance.”*
50
+
Then reload Cursor with `Developer: Reload Window`.
38
51
39
-
For API-key mode (no OAuth), set `LEADMAGIC_API_KEY` where Cursor can read it and apply the JSON block below.
52
+
### Option 3: Cursor marketplace
40
53
41
-
## MCP configuration
54
+
Install from the Cursor marketplace when the listing is available.
42
55
43
-
| Setting | Value |
44
-
| --- | --- |
45
-
| URL |`https://mcp.leadmagic.io/mcp`|
46
-
| Transport |`http`|
47
-
| Auth (default) | OAuth in Cursor (no `headers` in bundled `mcp.json`) |
56
+
## First run
48
57
49
-
**Optional API-key header** (merge into your MCP config; env var must be visible to Cursor):
58
+
1. Enable the LeadMagic plugin in Cursor.
59
+
2. Complete the OAuth sign-in flow when Cursor prompts you.
60
+
3. Ask Cursor something simple, such as:
61
+
62
+
```text
63
+
Check my LeadMagic credit balance.
64
+
```
65
+
66
+
You can also try:
67
+
68
+
```text
69
+
Validate this work email with LeadMagic: jane@company.com
70
+
Research the company acme.com with LeadMagic
71
+
Find people by role at Stripe: VP Marketing
72
+
```
73
+
74
+
## Authentication
75
+
76
+
### Default: OAuth
77
+
78
+
The bundled `mcp.json` uses OAuth by default. No API keys are stored in this repository.
79
+
80
+
### Optional: API-key mode
81
+
82
+
If you need header-based authentication instead of OAuth, set `LEADMAGIC_API_KEY` in an environment visible to Cursor and merge this into your MCP config:
50
83
51
84
```json
52
85
{
@@ -62,39 +95,98 @@ For API-key mode (no OAuth), set `LEADMAGIC_API_KEY` where Cursor can read it an
62
95
}
63
96
```
64
97
65
-
## Tools and documentation
98
+
On macOS, if Cursor cannot see `LEADMAGIC_API_KEY`, launch Cursor from a shell that already has the variable exported.
- REST and schemas: [LeadMagic OpenAPI](https://github.com/LeadMagic/leadmagic-openapi)
141
+
142
+
For direct `https://api.leadmagic.io` integration, OpenAPI schemas, or REST smoke tests, use the OpenAPI repository and product docs. The Cursor plugin exposes the hosted MCP surface, which is a subset of the full REST platform.
71
143
72
-
## Developing this repository
144
+
## Security and privacy
145
+
146
+
- Tool calls send the inputs you provide, such as emails, names, company domains, or profile URLs, to LeadMagic's hosted service.
147
+
- Never commit secrets, API keys, tokens, or `.env` files.
148
+
- Review [Privacy](https://leadmagic.io/privacy), [Terms](https://leadmagic.io/legal/terms), [Support](https://leadmagic.io/docs/support), and [SECURITY.md](SECURITY.md).
73
149
74
-
CI and local tooling target **Node.js 22** (see `.node-version` and `package.json``engines`).
150
+
## Develop this repository
151
+
152
+
This repo targets **Node.js 22**.
75
153
76
154
```bash
77
155
npm ci
78
156
npm run check
79
157
```
80
158
81
-
`npm run check` runs `npm run validate` (schema + package assertions) and `npm run verify:health` (GET `https://mcp.leadmagic.io/health`). **Offline:** use `npm run validate` only.
159
+
`npm run check` runs:
160
+
161
+
-`npm run validate` for schema and package assertions
162
+
-`npm run verify:health` for `GET https://mcp.leadmagic.io/health`
163
+
164
+
If you are offline, run:
82
165
83
166
```bash
84
-
npm run install:local # symlink into ~/.cursor/plugins/local/leadmagic
85
-
npm run uninstall:local # remove symlink
167
+
npm run validate
86
168
```
87
169
88
-
Marketplace copy and checklist: `SUBMISSION.md`. Changelog: `CHANGELOG.md`.
170
+
Useful local commands:
171
+
172
+
```bash
173
+
npm run install:local
174
+
npm run uninstall:local
175
+
```
176
+
177
+
Additional repo docs:
178
+
179
+
- Marketplace submission copy: `SUBMISSION.md`
180
+
- Release notes: `CHANGELOG.md`
89
181
90
182
## Troubleshooting
91
183
92
184
| Issue | What to try |
93
185
| --- | --- |
94
-
| OAuth / sign-in | Retry MCP settings; URL must be `https://mcp.leadmagic.io/mcp`; remove bad header overrides. |
95
-
|`LEADMAGIC_API_KEY` not seen (API-key mode) | On macOS, launch Cursor from a shell that has the var, or fix GUI env inheritance. |
0 commit comments