`ligand_interactions`

Pack: guidetopharmacology · Endpoint: https://gateway.pipeworx.io/guidetopharmacology/mcp

What proteins a drug acts on — the curated target interactions for a ligand in the Guide to PHARMACOLOGY (IUPHAR/BPS), each with the target PROTEIN NAME, interaction type (Agonist/Antagonist/Inhibitor), action and binding affinity (pKi/pIC50). Pass the drug by name (“imatinib”) and it is resolved for you; a GtoPdb ligand id also works. The response always names the ligand it actually read, so an id that turns out to be a different compound is visible rather than silent. Keyless.

Parameters

Name	Type	Required	Description
`ligand`	string	no	Drug/ligand name, e.g. “imatinib”. Resolved against the GtoPdb ligand list.
`ligand_id`	number,string	no	GtoPdb ligand id, e.g. 4139 for aspirin. Optional — give this OR ligand.
`limit`	number	no	Max interactions to return (default 25).

Example call

Arguments

{
  "ligand": "imatinib"
}

curl

curl -X POST https://gateway.pipeworx.io/guidetopharmacology/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ligand_interactions","arguments":{"ligand":"imatinib"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('ligand_interactions', {
  "ligand": "imatinib"
});

More examples

{
  "ligand_id": 4139
}

{
  "ligand_id": "4139",
  "limit": 40
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "guidetopharmacology": {
      "url": "https://gateway.pipeworx.io/guidetopharmacology/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

ligand_interactions