ChemCP vs MCP Pharma
A side-by-side look at the ChemCP and MCP Pharma MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ChemCP for biology & bioinformatics work as a local process; choose MCP Pharma for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ChemCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Choose MCP Pharma when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_PHARMA_API_KEY, MCP_PHARMA_API_BASE, MCP_PHARMA_TIMEOUT, MCP_PHARMA_LOG_LEVEL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | MCP_PHARMA_API_KEYMCP_PHARMA_API_BASEMCP_PHARMA_TIMEOUTMCP_PHARMA_LOG_LEVEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View ChemCP | View MCP Pharma |
Tools & capabilities
ChemCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Pharma tools
No tool names declared yet. Check the project README from the listing page.
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.
ChemCP
{
"mcpServers": {
"chemcp": {
"command": "npx",
"args": [
"-y",
"cloudflared"
]
}
}
}
MCP Pharma
{
"mcpServers": {
"mcp-pharma": {
"command": "uvx",
"args": [
"atomno-mcp-pharma"
],
"env": {
"MCP_PHARMA_API_KEY": "YOUR_MCP_PHARMA_API_KEY_HERE",
"MCP_PHARMA_API_BASE": "YOUR_MCP_PHARMA_API_BASE_HERE",
"MCP_PHARMA_TIMEOUT": "YOUR_MCP_PHARMA_TIMEOUT_HERE",
"MCP_PHARMA_LOG_LEVEL": "YOUR_MCP_PHARMA_LOG_LEVEL_HERE"
}
}
}
}
Frequently asked questions
ChemCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. MCP Pharma belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick ChemCP for biology & bioinformatics work and MCP Pharma for biology & bioinformatics.
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.
ChemCP has no declared pricing — check the project's own site. MCP Pharma has no declared pricing — check the project's own site. 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 chemcp and mcp-pharma as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ChemCP has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 2 GitHub stars. MCP Pharma has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.