Best for
- Researchers needing unified access to many scientific APIs, databases, models, and packages
- Developers building life-science, precision-oncology, or drug-discovery agents
- AI scientist projects using the CLI, Python SDK, or MCP integration
T
ToolUniverse MCP Server
Official
2,500+ scientific tools for AI scientists.
GitHub source repository ↗
51FMRS · D
ToolUniverse MCP Server targets science-focused AI agents, with broad coverage and support for tool discovery, execution, composition, asynchronous operations, and scientific data sources. It is best suited to research and development teams able to configure APIs and validate results.
ToolUniverse is an ecosystem for building AI scientist systems, covering life science, research, literature search, data analysis, and experimental design. Its MCP server supports compact mode, exposing a small set of core discovery and execution capabilities by default while retaining access to more than 2,500 tools.
Tools
The tool list has not been reviewed yet.
Setup
The recommended setup is to ask an AI agent to read https://aiscientist.tools/setup.md and configure MCP, API keys, skills, and validation. For manual setup, add the JSON in install_config to the MCP configuration file. Agent skills can also be installed with npx skills add mims-harvard/ToolUniverse. Use --refresh to check PyPI for the latest release at launch; omit it to use uv's cache.
claude_desktop_config.json
{"mcpServers":{"tooluniverse":{"command":"uvx","args":["--refresh","tooluniverse"],"env":{"PYTHONIOENCODING":"utf-8"}}}}
Fit and risk
Not for
- Users who need only a few general-purpose office or development tools
- Workflows that cannot configure any external scientific-service credentials
- Scenarios where AI-generated results will be treated as validated scientific conclusions
Required permissions
- Local execution of uvx and the ToolUniverse Python package
- Access to external APIs, databases, or model services used by selected tools
- Optional API keys for model, literature, patent, biomedical, and structure-prediction services
- Some tools may require locally installed extras or additional dependencies
Risks and side effects
- Scientific retrieval, analysis, and reasoning outputs require human validation
- Configured API keys are used with their corresponding external services
- External services may impose rate limits, credential requirements, or availability changes
- Loading many tools or running long tasks may increase resource usage and context-window pressure
Troubleshooting
- Confirm that uv is installed and start the server with uvx or the README configuration
- Run `tooluniverse-doctor` to identify missing extras
- Use `--refresh` when a current PyPI release is needed; clear the package cache with `uv cache clean tooluniverse` if necessary
- Use repeated `--categories` options to limit loaded tool categories and review compact-mode behavior
- Check API keys, registration status, and rate limits for the external services being used
Use cases
Life-science and drug-discovery research
Literature search across PubMed, Semantic Scholar, ArXiv, BioRxiv, Europe PMC, and more
Data analysis, knowledge retrieval, and experimental design
Long-running tasks such as protein docking and molecular simulations
Composable workflows for AI scientist systems
Supported clients
Supported clients have not been confirmed yet.