MCP — AI assistants
Lynqu ships a hosted Model Context Protocol server, so AI assistants can work your Lynqu account by natural language — “log everyone I met at the expo as leads”, “move Acme to Negotiation and draft a follow-up”.
Server endpoints
Section titled “Server endpoints”| Endpoint | Audience | Tools |
|---|---|---|
https://api.lynqu.com/mcp/v2 |
Organizations (Business/Enterprise seats) | Full B2B suite: leads, campaigns, events, team, dashboards, automation |
https://api.lynqu.com/mcp/me |
Individuals | Personal cards, card analytics, profile |
Connect a client
Section titled “Connect a client”Both endpoints speak streamable HTTP with OAuth. In any MCP-capable client (Claude, ChatGPT, Cursor, Windsurf, VS Code, …):
- Add a new MCP server / connector and paste the endpoint URL.
- Your browser opens a Lynqu consent page — sign in and approve.
- Done. No tokens to copy; the OAuth connection can be revoked from Lynqu at any time.
Desktop and CLI clients that register with a loopback redirect
(http://127.0.0.1, any port) are supported out of the box.
Plans and permissions
Section titled “Plans and permissions”- Connecting is open to any signed-in user.
- Running tools requires Pro+AI, Business, or Enterprise (your plan or your org seat).
- On the organization server every tool call re-checks your org role and the org’s MCP policy (admins can restrict which roles may use the assistant, or set it read-only). The assistant can never see or do more than you can in the app.
MCP vs. REST API
Section titled “MCP vs. REST API”| MCP | REST API | |
|---|---|---|
| Consumer | AI assistants | Your own code |
| Auth | OAuth consent flow | API keys |
| Plans | Pro+AI and up | Business and up |
| Shape | ~100 task-level tools | Resource endpoints |
If you’re building an integration, use the REST API. If you’re wiring an AI assistant, use MCP.