tooluniverse MCP Server

What this does

tooluniverse exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

OPENAI_API_KEY
ANTHROPIC_API_KEY
GEMINI_API_KEY
OPENROUTER_API_KEY
AZURE_OPENAI_API_KEY
HF_TOKEN
NCBI_API_KEY
SEMANTIC_SCHOLAR_API_KEY
BIOGRID_API_KEY
DISGENET_API_KEY
OMIM_API_KEY
ONCOKB_API_TOKEN
NVIDIA_API_KEY
USPTO_API_KEY
UMLS_API_KEY
BRENDA_EMAIL
BRENDA_PASSWORD

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install tooluniverse?

Run the Claude Code command in the install section to add tooluniverse to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with tooluniverse?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to tooluniverse as well.

Does tooluniverse need an API key?

Yes. Before it can run, set these environment variables: OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY, AZURE_OPENAI_API_KEY, HF_TOKEN, NCBI_API_KEY, SEMANTIC_SCHOLAR_API_KEY, BIOGRID_API_KEY, DISGENET_API_KEY, OMIM_API_KEY, ONCOKB_API_TOKEN, NVIDIA_API_KEY, USPTO_API_KEY, UMLS_API_KEY, BRENDA_EMAIL, BRENDA_PASSWORD. They go in the env block of your MCP config.