peptide_compare — TruePeptideSource MCP Tool
peptide_compare
(peptide compare) is one of 6 tools on the
TruePeptideSource
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call peptide_compare from your client
- Claude Code TruePeptideSource peptide_compare run in your project directory
- Claude Desktop TruePeptideSource peptide_compare ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TruePeptideSource peptide_compare ~/.cursor/mcp.json
- VS Code TruePeptideSource peptide_compare .vscode/mcp.json
- Zed TruePeptideSource peptide_compare ~/.config/zed/settings.json
- Windsurf TruePeptideSource peptide_compare ~/.codeium/windsurf/mcp_config.json
- Cline TruePeptideSource peptide_compare ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TruePeptideSource peptide_compare ~/.gemini/settings.json
- Grok TruePeptideSource peptide_compare .mcp.json (in your project root)
- ChatGPT TruePeptideSource peptide_compare Settings → Connectors → Advanced → Developer mode
- Claude.ai TruePeptideSource peptide_compare Settings → Connectors → Add custom connector
- LangChain TruePeptideSource peptide_compare pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http peptides https://truepeptidesource.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.