chore: align Cursor plugin with expanded MCP surface (v0.1.2)

Document ten hosted tools in README, rules, and skills. Update CHANGELOG and
plugin metadata so marketplace installs match mcp.leadmagic.io capabilities.

Made-with: Cursor

Author: jesseoue

.cursor-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
 	"name": "leadmagic",
 	"displayName": "LeadMagic",
-	"version": "0.1.0",
-	"description": "Official LeadMagic plugin for Cursor with hosted MCP-powered work email validation, email finding, account research, and credit-aware enrichment.",
+	"version": "0.1.2",
+	"description": "Official LeadMagic plugin for Cursor with hosted MCP: emails, mobile, LinkedIn-to-email, job changes, company research, competitors, technographics, and credits.",
 	"author": {
 		"name": "LeadMagic",
 		"email": "plugins@leadmagic.io"

CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to the LeadMagic Cursor plugin will be documented in this fi
 
 ## [Unreleased]
 
+### Changed
+- README, rules, and skills now describe the expanded hosted MCP tool set (mobile, LinkedIn-to-email, job change, competitors, technographics, people-by-role).
+- Rules: avoid speculative deliverability or catch-all commentary; stick to tool output for validation.
+- Aligns with hosted MCP email-validation summaries that surface `email_status` correctly.
+
 ### Added
 - Initial public Cursor plugin package structure
 - Hosted MCP configuration for `https://mcp.leadmagic.io/mcp`

README.md

@@ -10,7 +10,7 @@ The package includes:
 
 - Hosted LeadMagic MCP connectivity for Cursor
 - The current LeadMagic MCP surface:
-  - 4 tools for credit checks, work email validation, work email finding, and account research
+  - 10 tools: credits, work email validate/find, mobile, LinkedIn-to-email, job-change detection, account research, competitors, technographics, people-by-role
   - 1 shared docs resource: `leadmagic://docs`
   - 2 built-in prompts: `account_research` and `contact_lookup`
 - Four focused Cursor skills aligned to the current hosted MCP surface:
@@ -40,14 +40,13 @@ Users provide their API key through the `LEADMAGIC_API_KEY` environment variable
 
 ## What The MCP Supports Today
 
-The current hosted MCP surface is strongest for:
+The hosted MCP surface supports:
 
-- checking credit balance with `check_credit_balance`
-- validating known work emails with `validate_work_email`
-- finding likely work emails with `find_work_email`
-- researching companies with `research_account`
+- `check_credit_balance`, `validate_work_email`, `find_work_email`
+- `find_mobile_number`, `linkedin_profile_to_work_email`, `detect_job_change`
+- `research_account`, `list_company_competitors`, `get_company_technographics`, `find_people_by_role`
 
-The broader REST API and OpenAPI snapshot include additional surfaces, but this plugin is documented against the current hosted MCP surface only. That keeps the marketplace listing accurate and avoids implying support for endpoints that are not currently exposed through MCP.
+The broader REST API includes more endpoints (jobs, ads, analytics, etc.); this plugin tracks the hosted MCP tool list above. See `leadmagic://docs` in Cursor for the live tool reference.
 
 ## Quick Start
 

rules/leadmagic-usage.mdc

@@ -6,7 +6,7 @@ alwaysApply: true
 
 When this plugin is available:
 
-1. Prefer LeadMagic tools for work email validation, work email discovery, and account research before suggesting manual research.
+1. Prefer LeadMagic tools for work email validation, discovery, mobile lookup, LinkedIn-to-email, job-change checks, company research, competitors, technographics, and role-based people search before suggesting manual research.
 2. Minimize unnecessary credit spend:
    - For bulk or credit-sensitive work, check balance first with `check_credit_balance`.
    - If the user already has an email, validate it with `validate_work_email` before trying to find another one.
@@ -22,5 +22,6 @@ When this plugin is available:
    - the key results,
    - any important null, not-found, or unknown outcomes,
    - and any obvious next best step.
-6. If parameter requirements, supported inputs, or pricing are unclear, consult the shared MCP docs resource `leadmagic://docs` before guessing.
-7. If the API key is missing or authentication fails, tell the user they need to set `LEADMAGIC_API_KEY`.
+6. For email validation, summarize only what appears in the tool output (including the stated result line). Do not speculate about “missing” deliverability details, catch-all behavior, or fields the response does not include.
+7. If parameter requirements, supported inputs, or pricing are unclear, consult the shared MCP docs resource `leadmagic://docs` before guessing.
+8. If the API key is missing or authentication fails, tell the user they need to set `LEADMAGIC_API_KEY`.

skills/account-intelligence/SKILL.md

@@ -12,7 +12,7 @@ Use when the user wants company research, ICP fit, or a target account brief fro
    - company domain preferred,
    - otherwise company name.
 2. Run `research_account` to establish the canonical account record.
-3. Keep the work scoped to the current MCP surface. If the user asks for technographics, competitors, ad intelligence, or other API-only surfaces, be explicit that those may exist in the broader API/docs surface but are not part of the current hosted MCP tool set.
+3. When the user asks for a dedicated competitor list or tech stack, follow with `list_company_competitors` or `get_company_technographics`. Ad intelligence and other marketing APIs remain outside the hosted MCP tool set—say so if asked.
 4. Keep the summary operator-friendly:
    - what the company is,
    - why it matters,

skills/contact-enrichment/SKILL.md

@@ -10,6 +10,8 @@ Use when the user needs a validated work email or wants LeadMagic to find the li
 ## Workflow
 1. Start from the strongest identifier the user already has.
    - Existing work email: validate it first with `validate_work_email`.
+   - B2B profile URL (e.g. LinkedIn): use `linkedin_profile_to_work_email`; then validate if needed.
+   - Work email or profile URL + wants phone: `find_mobile_number`.
    - Full name + company or domain: use `find_work_email`.
 2. Prefer the cheapest path that can answer the question.
 3. If the user already has an email, do not jump straight to finding another one.
@@ -21,6 +23,7 @@ Use when the user needs a validated work email or wants LeadMagic to find the li
 - Existing email fails validation or no email exists -> `find_work_email`
 - Name + company + wants work email -> `find_work_email`
 - Person + company + wants confidence before spending more credits -> `check_credit_balance` -> `find_work_email`
+- Recent role change signal -> `detect_job_change` (email, profile URL, or name + company)
 
 ## Output
 Return:

skills/prospect-list-qc/SKILL.md

@@ -12,8 +12,10 @@ Use when the user has many prospects and wants the highest-confidence sequence f
 2. Prioritize validation before expensive enrichment whenever emails already exist.
 3. Separate records into buckets:
    - already have work email -> `validate_work_email`,
+   - have B2B profile URL -> `linkedin_profile_to_work_email` then validate if needed,
+   - have email or profile + need phone -> `find_mobile_number`,
    - have name + company only -> `find_work_email`,
-   - company-only records -> `research_account`.
+   - company-only records -> `research_account`; add `list_company_competitors` or `get_company_technographics` when the list needs those angles.
 4. Remove duplicates before enrichment.
 5. Preserve null and unknown outcomes instead of forcing guesses.
 6. Recommend the cheapest sensible order of operations before bulk runs.

skills/signal-research/SKILL.md

@@ -12,7 +12,7 @@ Use when the user wants evidence that an account is relevant now and needs a con
 2. Use `research_account` to collect the strongest current account context LeadMagic can provide through MCP.
 3. Synthesize the results into GTM implications, not just raw data.
 4. Highlight uncertainty when signals are partial or the hosted MCP surface does not expose the exact field the user wants.
-5. Stay within the current MCP surface. If the user asks for jobs, competitors, funding, technographics, or ad intelligence, call out that those may belong to the wider API/docs surface rather than the current hosted MCP tool set.
+5. Stay within the hosted MCP tools. Competitors and technographics are available via `list_company_competitors` and `get_company_technographics`. Job postings and ad intelligence are not in MCP—point to the REST docs if the user needs those.
 
 ## Output
 Return: