Cursor Bindingdb bindingdb_ligands_by_uniprot
How to: Cursor Bindingdb bindingdb_ligands_by_uniprot
Add Bindingdb to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"bindingdb": {
"url": "https://gateway.pipeworx.io/bindingdb/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something bindingdb_ligands_by_uniprot does. Cursor lists the server's tools on connect and calls bindingdb_ligands_by_uniprot itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Bindingdb's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Bindingdb will not start until these are set, so bindingdb_ligands_by_uniprot never becomes available.
-
PIPEWORX_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.