Lynqu AI Toolkit

Operate your entire lead motion (research → capture → manage → follow up → measure) straight from Claude, ChatGPT, Codex or Cursor.

Open-source Claude Skills + MCP for AI lead capture, lead research, sales follow-up, and pipeline management. Powered by Lynqu.

 

---

✨ What this does

Connect Lynqu to your AI assistant, then run your sales motion in plain language. No dashboards, no data entry, no context-switching.

You ▸ I met ~30 people at the SaaStr booth. Here's the list [paste].
      Dedupe against our contacts, add the new ones to the Events pipeline,
      tag them SaaStr-2026, and draft follow-ups for the hot ones.

Lynqu AI ▸ Working through it…
   🔎  Checked 30 contacts → 22 new, 8 already in your pipeline (skipped)
   ➕  Created 22 leads in "Events" at the New stage
   🏷️  Tagged SaaStr-2026 · attached to the SaaStr campaign
   🔥  6 flagged hot (asked for a demo). Drafts ready below for your review
   ✅  Done. Want me to send the 6 follow-ups, or tweak them first?

That whole flow is one sentence to you, and a chain of audited Lynqu actions under the hood. The skill is the recipe; the MCP is the hands.

---

⚡ Quick start

1. Connect the Lynqu MCP server (OAuth, no API key to copy):

Server	URL	Scope
Organization (B2B)	https://api.lynqu.com/mcp/v2	Cards, contacts, leads, campaigns, events, pipeline, team, follow-ups, AI employees, analytics
Personal	https://api.lynqu.com/mcp/me	Your own cards, card analytics, profile

Then, in your client:

• Claude (claude.ai, Desktop): Settings → Connectors → Add custom connector, paste the URL, sign in. Claude Code: claude mcp add --transport http lynqu https://api.lynqu.com/mcp/v2
• ChatGPT (Plus, Pro, Business, Enterprise, Edu): turn on Developer mode, open chatgpt.com/plugins → + → Add custom MCP server, paste the URL, keep OAuth, sign in on the Lynqu page. Then call it with @Lynqu in a chat.
• Codex (app or CLI): Settings → MCP servers → Add, Streamable HTTP, paste the URL, then Authenticate. CLI: codex mcp add lynqu --url https://api.lynqu.com/mcp/v2 and codex mcp login lynqu.
• Cursor, VS Code and any other MCP client: add a remote HTTP server with the URL and approve on the Lynqu page.

Full per-client steps, with the gotchas, are in docs/mcp/connect.md. There is also a one-click setup in the Lynqu app under Settings → AI / MCP.

2. Install the skills. The method depends on where you use Claude:

git clone https://github.com/Gravisun/lynqu-ai-toolkit.git
cp -r lynqu-ai-toolkit/skills/lynqu* ~/.claude/skills/

~/.claude/skills is Claude Code only; everywhere else (including the Claude desktop app) each skill is uploaded as its own ZIP. Needs a Pro, Max, Team or Enterprise plan.

1. Turn on Settings → Capabilities → Code execution and file creation (without it the Skills section does nothing).

2. Grab the ready-made ZIPs from the latest release, or build them yourself. The skill folder must be the root of the archive, not the loose files and not a wrapper directory:

   git clone https://github.com/Gravisun/lynqu-ai-toolkit.git
   cd lynqu-ai-toolkit/skills
   for s in lynqu*; do zip -r "../$s.zip" "$s"; done
   

3. Settings → Customize → Skills → Add and upload the ZIPs one at a time.

⚠️ Writing your own skill? Keep description under 200 characters. Anthropic's documented ceiling is 1024, but the description sits in context permanently and is the text Claude matches your request against. Short and specific triggers better, and uploads cleanly on every surface. python3 scripts/validate_skills.py enforces it.

3. Just ask:

"Research 10 fintech targets in London, qualify them for Lynqu, and create leads for the best fits."

That's it. See examples/prompts.md for a full prompt library.

💡 Plan note: connecting is free on any account. Running tools needs an AI-tier plan (Pro+AI, Business+AI or Enterprise).

---

🛠️ The skills

Seventeen skills covering the whole motion. You don't need to learn them. Say what's going on and lynqu works out which ones to run, in what order.

/lynqu we just got back from SaaStr with 200 badges and I don't know where anything is

Routes to event → capture → qualify → outreach, confirming before each write.

Or drive them directly:

This is the beginning of the README. Read the rest at the original. Read the full README ↗