mims-harvard/tooluniverse15 files

Setup Tooluniverse

Install and configure ToolUniverse for any use case — MCP server (chat-based), CLI (command line with 14 subcommands), or Python SDK (Coding API with 3 calling patterns). Covers uv/uvx setup, MCP configuration for 12+ AI clients (Cursor, Claude Desktop, Windsurf, VS Code, Codex, Gemini CLI, Trae, Cline, etc.), full CLI reference (tu list/grep/info/find/run/test/status/build/remote/doctor/serve/connect/connections/disconnect), Coding API quickstart, agentic tools, code executor, API key walkthrough, skill installation, and upgrading. Use when user asks how to set up ToolUniverse, which access mode to use (MCP vs CLI vs SDK), configuring MCP servers, using the CLI, troubleshooting installation, upgrading, or mentions installing ToolUniverse or setting up scientific tools. Also triggers for "how do I use ToolUniverse", "what's the best way to access tools", "command line", "tu command", "coding API", "tu build".

Specification
Skill ID
mims-harvard/tooluniverse/setup-tooluniverse
Publisher
mims-harvard
Repository
tooluniverse
Installs
0
Files
15
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

mims-harvard/tooluniverse/setup-tooluniverseInstalls these files
  • API_KEYS_REFERENCE.md
  • CLAUDE_DESKTOP.md
  • EXAMPLES.md
  • GITHUB_ISSUE.md
  • INSTALL.md
  • MCP_CONFIG.md
  • SKILL.md
  • SKILLS_CATALOG.md
  • TRAE.md
  • TROUBLESHOOTING.md
  • references/mcp-configs.md
  • scripts/check_prerequisites.py
  • scripts/diagnose_setup.py
  • scripts/list_tool_categories.py
  • scripts/verify_installation.py

What this skill tells the agent

Setup ToolUniverse

Guide the user step-by-step through setting up ToolUniverse.

Agent Behavior

  • Detect language from user's first message. Respond in their language; keep commands/URLs in English.
  • Go one step at a time. Ask before proceeding.
  • Use AskQuestion for structured choices.
  • Explain briefly in plain language. Celebrate small wins.
  • When something goes wrong, help troubleshoot before moving on.

Internal Notes (do not show)

ToolUniverse has 2,700+ tools. The tooluniverse command enables compact mode automatically, exposing only 5 core MCP tools (list_tools, grep_tools, get_tool_info, execute_tool, find_tools) while keeping all tools accessible via execute_tool.

What is ToolUniverse?

Always explain first, in plain language:

ToolUniverse is free, open-source software connecting to 2,000+ scientific databases (PubMed, UniProt, ChEMBL, FAERS, ClinicalTrials.gov, etc.). Instead of visiting each website, you search from one place. Think of it like a universal remote for scientific databases.

Why AI assistants? The AI reads your question, figures out which databases to search, runs queries, and summarizes results. You just ask your question.

Step 1: Choose How to Use It

Present using AskQuestion:

ModeWhat it meansWho it's for
Chat modeAsk questions to an AI assistant. No coding.Most researchers.
Command lineType short commands in Terminal.Quick tests. Terminal-comfortable users.
Python codeWrite scripts for automated pipelines.Programmers.

Options: "I want to ask questions" → Chat mode | "Quick try" → CLI | "I write Python" → SDK | "I don't know" → Recommend Chat mode

If Chat mode, ask which app (AskQuestion): Cursor, Claude Desktop, VS Code/Copilot, Windsurf, Claude Code, Gemini CLI, Codex, Cline/Trae/Antigravity/OpenCode. "I don't have any" → Recommend Claude Desktop.

Step 2: Install uv

Only prerequisite: uv (manages everything else automatically).

Terminal help (if needed): Mac: Cmd+Space → "Terminal" → Enter. Windows: Win key → "PowerShell" → Enter.

curl -LsSf https://astral.sh/uv/install.sh | sh

(This is a safe, standard command that downloads and installs uv, a small package manager. It's widely used by Python developers. Close and reopen your terminal after it finishes.)

Verify: uv --version

CLI Setup

Make sure Step 2 is done, then try:

uvx --from tooluniverse tu status              # How many tools?
uvx --from tooluniverse tu find 'drug safety'  # Search by topic
uvx --from tooluniverse tu info FAERS_count_death_related_by_drug  # See params
uvx --from tooluniverse tu run FAERS_count_death_related_by_drug '{"medicinalproduct": "metformin"}'

First run takes ~30s (downloads package), then instant. Shortcut: uv tool install tooluniverse → then just use tu directly.

All CLI subcommands

CommandWhat it doesExample
tu statusShow tool count and top categoriestu status
tu listList tools (modes: names, categories, basic, by_category, summary, custom)tu list --mode basic --limit 20
tu findSearch by natural language (keyword scoring, no API key needed)tu find 'protein structure analysis'
tu grepText/regex pattern searchtu grep '^UniProt' --mode regex
tu infoShow tool parameters and schematu info PubMed_search_articles
tu runExecute a tooltu run PubMed_search_articles '{"query": "CRISPR"}'
tu testTest a tool with its example inputstu test UniProt_get_entry_by_accession
tu buildGenerate typed Python wrappers for Coding API (also regenerates the internal lazy-load registry in place — unaffected by --output)tu build --output ./my_tools
tu serveStart MCP stdio server (same as uvx tooluniverse)tu serve

Output flags (most commands except build/serve): --json (pretty) or --raw (compact, pipe-friendly).

Continue to Step 3 (API Keys).

SDK Setup

Install `uv` first (Step 2). Do not use system `pip`. On a current Mac (Homebrew Python 3.13/3.14) pip install tooluniverse stops with error: externally-managed-environment (PEP 668), and python3 -m venv can fail at ensurepip. uv avoids both because it downloads and manages its own Python.
uv venv --python 3.12          # own Python + virtualenv, ignores system pip
source .venv/bin/activate      # Windows: .venv\Scripts\activate
uv pip install tooluniverse

uv pip install needs an active virtualenv — run uv venv first, or use uv tool install tooluniverse if you only want the tu command.

For detailed patterns, invoke the tooluniverse-sdk skill.

Optional extras: the base install covers API/database tools. Local ML, cheminformatics, and plotting tools need extras — uv pip install 'tooluniverse[ml]', [visualization], [bioinformatics], or [all]. Run tooluniverse-doctor to see which groups you are missing. Note [all] does not include singlecell, smolagents, client, or build; install those separately.

Coding API — 3 calling patterns

Pattern 1: Direct import (typed, with autocomplete):

from tooluniverse.tools import UniProt_get_entry_by_accession
result = UniProt_get_entry_by_accession(accession="P12345")

Pattern 2: Attribute access (no import needed per tool):

from tooluniverse import ToolUniverse
tu = ToolUniverse()
tu.load_tools()
result = tu.tools.UniProt_get_entry_by_accession(accession="P12345")

Pattern 3: JSON-based (dynamic, for pipelines):

result = tu.run({"name": "UniProt_get_entry_by_accession", "arguments": {"accession": "P12345"}})

Generate typed wrappers: tu build (creates importable Python modules with autocomplete).

Agentic Tools & Code Executor

ToolUniverse also includes 23 AI-powered agentic tools (ScientificTextSummarizer, HypothesisGenerator, ExperimentalDesignScorer, peer-review tools, etc.) and 2 code executor tools (python_code_executor, python_script_runner). These are called like any other tool — via tu.run() or execute_tool(). Agentic tools require an LLM API key (e.g., OPENAI_API_KEY).

Continue to Step 3 (API Keys).

MCP Setup (Chat Mode)

Offer the two low-effort paths first. Editing JSON by hand is the fallback, not the recommendation — a mistyped comma is the single most common setup failure. Only walk through the manual path if neither option below fits.

Path A — let an AI agent do it. If the user already has any agent (Claude, Cursor, Copilot, Gemini, Codex...), they can paste this into it:

Read https://aiscientist.tools/setup.md and set up ToolUniverse for me.

The agent handles config, keys, skills, and validation. No terminal, no JSON.

Path B — Claude Code or Codex users: one-liner, no config file at all.

Claude Code:

claude plugin marketplace add mims-harvard/ToolUniverse
claude plugin install tooluniverse@tooluniverse

See the tooluniverse-claude-code-plugin skill's "Recommended: turn on auto-update" step so future releases apply without manual claude plugin update.

Codex:

codex plugin marketplace add mims-harvard/ToolUniverse
codex plugin add tooluniverse -m tooluniverse

See the tooluniverse-codex-plugin skill for verification, updates, and troubleshooting.

Both install the MCP server plus 180+ skills in one step. Google Antigravity users: see the tooluniverse-antigravity-plugin skill instead — its install flow differs (agy plugin install, not a marketplace add).

Manual config (fallback)

Make sure Step 2 is done (uv --version works).

Use this skill in a project

Open any RiverX project, search the Skills panel for mims-harvard/tooluniverse/setup-tooluniverse, and install it in one click.

Use this skill