About ZOOQ - LinkedIn Data for AI Agents
ZOOQ provides AI agents with live LinkedIn data through a hosted MCP endpoint, without using the agent operator’s LinkedIn account. Its tools cover profiles, companies, jobs, posts, search signals, and email finding.
Key features
- 01LinkedIn profile and company data
- 02People and company search
- 03Job listings and hiring teams
- 04Posts and activity data
- 05Email finding and verification
Use cases
- 01Research a company and its employees
- 02Find prospects matching search criteria
- 03Track job-change signals at target accounts
- 04Identify and verify contact email addresses
MCP support
ZOOQ exposes 44 tools through a hosted streamable HTTP MCP endpoint, authenticated with an X-API-Key header.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://zooq.dev/api/mcpclaude mcp add --transport http baldiga-zooq https://zooq.dev/api/mcp{"mcpServers":{"baldiga-zooq":{"type":"http","url":"https://zooq.dev/api/mcp"}}}Open in Cursor{"servers":{"baldiga-zooq":{"type":"http","url":"https://zooq.dev/api/mcp"}}}Open in VS Code{"mcpServers":{"baldiga-zooq":{"type":"http","url":"https://zooq.dev/api/mcp"}}}{"mcpServers":{"baldiga-zooq":{"serverUrl":"https://zooq.dev/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://zooq.dev/api/mcpAuth requiredTools
45| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | No | Stable profile id (prsn_...). Get it from profile_full or /search/people — read data.id. Provide handle OR id. |
| handle | string | No | Public profile handle. Provide handle OR id. |
Details
From the project READMEZOOQ MCP — live LinkedIn data for AI agents
ZOOQ gives your AI agent real-time LinkedIn data — profiles, companies, jobs, posts, people search, job-change signals and email finding — as 44 clean MCP tools served from a hosted endpoint.
The important part: your agent never touches your LinkedIn account. Most LinkedIn MCP servers work by borrowing your logged-in session cookie, which puts your own account at ban risk and breaks every few weeks. ZOOQ runs on its own infrastructure. You paste one API key; your account stays out of it entirely.
- Endpoint:
https://zooq.dev/api/mcp(streamable HTTP) - Auth:
X-API-Keyheader — get a free key (300 credits, no card) - Pricing: credit-based, pay for what you call. Failed upstream calls are auto-refunded.
Install
Claude Code
claude mcp add --transport http zooq https://zooq.dev/api/mcp --header "X-API-Key: YOUR_ZOOQ_KEY"
Cursor / Cline / any MCP client (config JSON)
{
"mcpServers": {
"zooq": {
"url": "https://zooq.dev/api/mcp",
"headers": { "X-API-Key": "YOUR_ZOOQ_KEY" }
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector → URL https://zooq.dev/api/mcp, header X-API-Key: YOUR_ZOOQ_KEY.
Replace YOUR_ZOOQ_KEY with the key from zooq.dev/signup. That's the whole setup.
What your agent can do with it
| Category | Tools | Examples |
|---|---|---|
| Profiles (7) | full profile, enrich, employment history, similar people | profile_full, profile_enrich |
| Companies (11) | company info, employees data, insights, similar companies | companies_enrich, companies_employees_data |
| Search & signals (7) | people/company search, live search, job-change signals | search_people, search_job_changes |
| Jobs (6) | job search, details, hiring team | search_jobs, jobs_hiring_team |
| Posts & activity (5) | a person's posts, comments, likes | posts_all, posts_comments |
| Email finding (5) | find, verify, reverse lookup, domain prospects | email_find_by_profile, email_verify |
| Lookups (3) | skills, institutions taxonomy | g_title_skills_lookup |
Typical agent recipes:
- AI SDR —
search_people→profile_enrich→posts_all→ write a genuinely personalized opener →email_find_by_profile - Job-change trigger —
search_job_changeson your target accounts → congratulate/pitch the week they land - Account research —
companies_enrich+companies_employees_data+companies_jobs→ a briefing your agent writes itself
Why not a scraper or a cookie-based server?
| Cookie/scraper servers | ZOOQ | |
|---|---|---|
| Uses YOUR LinkedIn account | Yes — ban risk is yours | Never |
| Breaks when LinkedIn changes | Constantly | Our problem, not yours |
| Setup | Browser profiles, cookies, captchas | One API key |
| Cost | "Free" until your account isn't | 300 free credits, then pay-per-call |
Rate limits & good citizenship
Responses carry _meta.credits_remaining and _meta.hourly_cap_remaining — agents should pace themselves.
Default cap: 10,000 credits/hour. Errors are structured (-32005 = hourly cap, back off).
Links
- Site & docs: zooq.dev
- Free key: zooq.dev/signup
- Pricing: zooq.dev/pricing
- Built by Amir Baldiga — GTM engineer; ZOOQ powers his own outbound agents.
License
MIT (this repository — the metadata and docs). The ZOOQ API itself is a commercial service.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.