Interacting with the Drug Gene Interaction Database (DGIdb) via Claude Desktop

Created By
QuentinCodya year ago
Overview

What is DGIdb MCP Server?

DGIdb MCP Server is a software tool that allows users to interact with the Drug Gene Interaction Database (DGIdb) through the Claude Desktop application, enabling queries about drug-gene interactions in plain language.

How to use DGIdb MCP Server?

To use the DGIdb MCP Server, you need to set it up and connect it to your Claude Desktop application. Once configured, you can ask Claude questions about drug interactions, and it will fetch the information from DGIdb.

Key features of DGIdb MCP Server?

  • Connects Claude Desktop to the DGIdb API for easy querying.
  • Allows users to ask natural language questions about drug-gene interactions.
  • Supports deployment on platforms like Cloudflare Workers.

Use cases of DGIdb MCP Server?

  1. Researchers can query drug interactions for specific genes.
  2. Pharmacologists can find drug attributes and interactions.
  3. Educators can use it to teach about drug-gene relationships.

FAQ from DGIdb MCP Server?

  • What is DGIdb?
    DGIdb is a comprehensive database that provides information on how drugs interact with genes.

  • Is there a citation requirement for academic use?
    Yes, if you use this software in a research project that leads to a publication, you must cite it according to the provided format.

  • Can I deploy the server on my own?
    Yes, technical users can deploy the server on platforms like Cloudflare Workers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
QuentinCody
Star
0
Language
TypeScript
License
View license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago