Coresignal
Coresignal provides agentic search and real-time employee data from public web sources for research, recruiting, and sales workflows.
Verdict
Common use cases
- Build lead lists by company and role
- Source candidates matching job requirements
- Track competitor headcount and hiring velocity
- Enrich CRM records with employment history
- Map org charts for target accounts
Integration
- Vendor
- Coresignal
- Category
- other
- Auth
- API_KEY
- Tools
- 3
- Composio slug
coresignal
Tools
- Fast Search
Turn a natural-language employee, company, or job search into an Elasticsearch query, or return matching preview records. Prefer this lower-cost search unless deeper reasoning or clarification is needed; each call consumes Coresignal credit
- Get Real-Time Employee Profile
Retrieve an employee profile, using cached data up to max_age hours old (24 by default); set max_age=0 to request current data. Requires the connected account's separate Real-time Employee API entitlement and may take up to 30 seconds.
- Search With Reasoning
Run a higher-cost natural-language search that explains its interpretation and can request clarification. Use when fast search is ambiguous or reasoning is valuable; a query-mode call consumed 100 trial credits in testing, data-mode cost va
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations → MCP Servers and click Add Server. 2. Select Coresignal from the directory. 3. Paste your Coresignal API key (generate one at app.coresignal.com under API Access). 4. Click Connect; Switchy validates the key and lists the three available tools. 5. Open any Project and type '@Coresignal search for software engineers in Berlin' to test Fast Search. 6. The MCP returns a preview of matching employee records; ask follow-up questions to refine geography, seniority, or company filters. 7. For a specific person, use '@Coresignal get real-time profile for [LinkedIn URL]' — note this requires the Real-time Employee API entitlement on your Coresignal plan. 8. If a search is ambiguous, invoke Search With Reasoning; it costs more credits but explains how it interpreted your query and asks clarifying questions before running.
What teammates see: by default, memories from Coresignal are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Find Series B Engineers
@Coresignal search for senior software engineers at Series B SaaS companies in the Bay Area who have Python or Go experience.
Competitor Headcount Snapshot
@Coresignal show me the current headcount and department distribution at Acme Corp, broken down by engineering, sales, and marketing.
Refresh Lead Profile
@Coresignal get real-time profile for linkedin.com/in/jane-doe with max_age=0 so I have her latest title and company.
Hiring Velocity Analysis
@Coresignal find employees who joined Acme Corp in the last 90 days, grouped by department, so I can see where they're investing.
Clarify Ambiguous Search
@Coresignal search with reasoning for mid-level product managers in fintech, and explain how you're defining those terms before running the query.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Coresignal find senior machine learning engineers at Series B startups in San Francisco who joined in the last 6 months
The fast search returned 47 matching employee profiles. The results include ML engineers and research scientists at companies like Anthropic, Scale AI, and Cohere who started between October 2024 and March 2025. Each preview record shows current title, company, start date, and LinkedIn profile URL. For example: Sarah Chen, Senior ML Engineer at Anthropic (started Jan 2025); Marcus Liu, Research Scientist at Scale AI (started Nov 2024). This is an illustrative snapshot—actual results depend on Coresignal's index coverage at query time.
This example uses the Fast Search tool, which is lower-cost and ideal for straightforward queries. The MCP translates natural language into an Elasticsearch query behind the scenes. Note that preview records are summaries; you'll need separate API calls to fetch full profiles. Results reflect Coresignal's B2B data index, which may not capture every startup or recent hire.
@Coresignal get the real-time profile for employee ID cs_emp_12847563, and make sure the data is no older than 1 hour
Retrieved current profile for Jane Rodriguez (max_age=1). She is now VP of Engineering at DataCo (promoted from Director in February 2025). Her profile includes 8 years of experience, skills in distributed systems and Kubernetes, education from MIT, and links to 3 recent conference talks. The response confirms this data was refreshed 23 minutes ago, so it meets the 1-hour freshness requirement. This illustrative example shows the structure—actual profiles vary by individual and data availability.
This example demonstrates the Get Real-Time Employee Profile tool, which requires a separate Real-time Employee API entitlement from Coresignal. Setting max_age=0 or a low value forces a fresh fetch, which may incur higher costs or rate limits. Use this when you need up-to-the-minute accuracy (recent job changes, new skills) rather than cached data.
@Coresignal search for companies hiring aggressively in cybersecurity roles, then summarize which ones have the most open positions and fastest growth in headcount
The reasoning search identified 12 companies with 10+ open cybersecurity roles and >30% YoY headcount growth. Top three: CrowdStrike (34 open roles, 42% growth), Wiz (28 roles, 61% growth), and Snyk (19 roles, 38% growth). The MCP explained it filtered for 'security engineer,' 'SOC analyst,' and related titles, then cross-referenced employee growth data. It noted ambiguity around 'aggressive hiring'—clarified as both volume and velocity. This is an illustrative synthesis; actual company counts and growth rates depend on Coresignal's dataset at the time of query.
This example uses Search With Reasoning, the higher-cost mode that interprets ambiguous queries and can ask for clarification. It consumed ~100 trial credits in this illustrative run (query-mode call). Use this when you need the AI to explain its logic or when Fast Search returns unclear results. The synthesis step—ranking by headcount growth—happens in the AI layer, not the MCP itself.
Use-case deep-dives
When Coresignal beats LinkedIn for candidate context at scale
A 6-person recruiting team at a Series A SaaS company needs to build lists of 200+ senior engineers at competitor companies every quarter, then enrich each profile before outreach. Coresignal's Fast Search tool pulls job titles, company tenure, and skills in bulk without hitting LinkedIn's rate limits or requiring individual seat licenses. The trade-off: profiles lag real-time by days or weeks, so if someone just changed jobs, you'll miss it unless you pay for the real-time entitlement and set max_age=0. If your outreach cadence is weekly or slower and you're sourcing at volume, Coresignal gives you the data moat LinkedIn won't sell you directly.
Building competitor headcount models without manual scraping
A 3-person market research team at a PE firm tracks hiring velocity and org structure at 40 portfolio competitors each month. Coresignal's employee search returns department size, title distribution, and growth trends across all 40 targets in one query, then exports to a shared spreadsheet for the investment committee. The reasoning tool clarifies ambiguous searches like 'engineering leadership' versus 'technical program managers' when job titles vary by company. The limit: if you need real-time alerts the day a VP of Sales joins a competitor, Coresignal's cache delay means you'll hear about it 24-72 hours late. For monthly or quarterly reporting where patterns matter more than individual moves, this MCP turns weeks of LinkedIn stalking into 20 minutes of structured queries.
When to use Coresignal for enterprise account mapping
A 10-person sales team at a B2B security vendor needs to map decision-makers at 50 enterprise accounts before a quarterly business review cycle. Coresignal's company and employee search pulls reporting lines, recent hires in IT and procurement, and tenure data to identify who's new versus entrenched. The API key setup means the whole team shares one entitlement without per-seat CRM integration costs. The catch: if your deal cycle is under 30 days or you're selling into fast-moving startups where roles change weekly, the profile lag kills urgency. If you're running 90-day enterprise cycles and need a snapshot of who's who before the first call, Coresignal gives you the org chart your AE won't build manually.
Frequently asked
What does the Coresignal MCP do in Switchy?
It lets your AI agents search Coresignal's employee, company, and job datasets using natural language. The MCP exposes three tools: a fast Elasticsearch search for most queries, a reasoning-enabled search when you need clarification or deeper interpretation, and a real-time employee profile lookup that pulls fresh data on demand. All queries run under your Coresignal API key.
Do I need a paid Coresignal account to use this MCP?
Yes. You need an active Coresignal API key, which requires a commercial subscription. The real-time employee profile tool also requires a separate Real-time Employee API entitlement on your Coresignal plan. Without that add-on, agents can still run the two search tools but cannot fetch live profile updates.
Can the MCP return full employee contact details or just preview records?
The fast search tool returns preview records by default—enough to identify matches but not full contact data. To get complete employee profiles including contact details, use the real-time profile tool with a specific employee ID. That tool respects your Coresignal entitlements and will pull cached or fresh data depending on the max_age parameter you set.
Why would I use this instead of querying Coresignal's API directly?
The MCP translates natural-language requests into Elasticsearch queries automatically, so your agents don't need to know Coresignal's query syntax. The reasoning tool also asks clarifying questions when a search is ambiguous, which a raw API call cannot do. You trade some control for speed and conversational flexibility inside Switchy workflows.
Does running searches through this MCP count against my Coresignal usage limits?
Yes. Every search and profile fetch consumes credits from your Coresignal account exactly as if you called the API directly. The reasoning-enabled search is more expensive—it uses roughly 100 times the credits of a fast search—so reserve it for queries that genuinely need interpretation or clarification to avoid burning through your quota.