find_peptide_sources — PepEvolution Peptide Sources MCP Tool Read-only
find_peptide_sources
(find peptide sources) is one of 3 tools on the
PepEvolution Peptide Sources
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_peptide_sources from your client
- Claude Code PepEvolution Peptide Sources find_peptide_sources run in your project directory
- Claude Desktop PepEvolution Peptide Sources find_peptide_sources ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PepEvolution Peptide Sources find_peptide_sources ~/.cursor/mcp.json
- VS Code PepEvolution Peptide Sources find_peptide_sources .vscode/mcp.json
- Zed PepEvolution Peptide Sources find_peptide_sources ~/.config/zed/settings.json
- Windsurf PepEvolution Peptide Sources find_peptide_sources ~/.codeium/windsurf/mcp_config.json
- Cline PepEvolution Peptide Sources find_peptide_sources ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PepEvolution Peptide Sources find_peptide_sources ~/.gemini/settings.json
- Grok PepEvolution Peptide Sources find_peptide_sources .mcp.json (in your project root)
- ChatGPT PepEvolution Peptide Sources find_peptide_sources Settings → Connectors → Advanced → Developer mode
- Claude.ai PepEvolution Peptide Sources find_peptide_sources Settings → Connectors → Add custom connector
- LangChain PepEvolution Peptide Sources find_peptide_sources pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http peptide-sources https://pepevolution.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.