Coresignal MCP vs Context7
A side-by-side look at the Coresignal MCP and Context7 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Coresignal MCP for developer tools work over a hosted endpoint; choose Context7 for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Coresignal MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
entity_search, entity_fields, entity_fetch.
Choose Context7 when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: API key required.
- You want tools like
resolve-library-id, query-docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 48/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 63,506 |
| Directory activity | 0 views 0 installs 0 upvotes | 14 views 0 installs 0 upvotes |
| Tools | 5 | 2 |
| Full listing | View Coresignal MCP | View Context7 |
Tools & capabilities
Coresignal MCP tools 5
entity_searchNatural-language search over employees, companies, or jobsentity_fieldsKeyword search over an entity's ~300 field namesentity_fetchPull full (JSONL) or projected records, by search handle or by idemail_enrichVerified business emails for employee ids (CSV)artifact_readPage rows back out of a delivered file
Context7 tools 2
resolve-library-idResolves a general library name into a Context7-compatible library ID.query-docsRetrieves documentation for a library using a Context7-compatible library ID.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Coresignal MCP
{
"mcpServers": {
"mcp-77": {
"url": "https://mcp.coresignal.com/mcp/v2"
}
}
}
Context7
No confirmed install command for Context7 yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Coresignal MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Context7 belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Coresignal MCP for developer tools work and Context7 for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Context7 has no confirmed install command yet — follow its own setup instructions.
Coresignal MCP has no declared pricing — check the project's own site. Context7 is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-77 and upstash-context7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coresignal MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Context7 has 55/100 (Good) with 14 views, 0 installs and 63,506 GitHub stars.