Tooluniverse MCP Server

Tooluniverse MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 1000+ scientific tools for AI scientists: life science, reserach, literature, and more.

What you get

Add to your MCP config file: json { "mcpServers": { "tooluniverse": { "command": "uvx", "args": ["--refresh", "tooluniverse"], "env": {"PYTHONIOENCODING": "utf-8"} } } }

ToolUniverse is an ecosystem for creating AI scientist systems from any large language model. Powered by the AI-Tool Interaction Protocol, it standardizes how LLMs identify and call tools, integrating more than 1000 machine learning models, datasets, APIs, and scientific packages for data analysis, knowledge retrieval, and experimental design.

Setting it up

skills on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: PYTHONIOENCODING. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by mims-harvard; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tooluniverse mcp server does with a few real requests.