
MaBoSS Boolean Network Simulator
- 18 repo stars
- Updated July 2, 2026
- marcorusc/mcp-biomodelling-servers
MaBoSS is an MCP server that runs Boolean network simulation and attractor analysis via MaBoSS from your agent.
About
MaBoSS Boolean Network Simulator is an MCP server that lets AI coding agents run Boolean network simulations and attractor analysis through MaBoSS instead of manual CLI scripting. It targets developers and small research teams who ship agent-assisted pipelines in computational biology, drug-discovery tooling, or teaching platforms and need repeatable simulation steps inside Claude Code or Cursor. Install via uvx with --from mcp-biomodelling-servers and the mcp-maboss-server positional argument. Use it when you are validating network hypotheses, batching attractor runs from chat, or documenting simulation parameters alongside code. It is niche compared to general dev MCP servers but matters when Boolean models are core to your product or research stack. Expect advanced biology and MaBoSS familiarity; the server does not replace domain expertise or wet-lab validation.
- MaBoSS Boolean network simulation exposed as MCP tools
- Attractor analysis for regulatory and signaling network models
- Stdio transport via uvx from PyPI package mcp-biomodelling-servers
- Entry point mcp-maboss-server in the marcorusc biomodelling server repo
- Version 1.0.0 with MCP server schema 2025-12-11
MaBoSS Boolean Network Simulator by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
claude mcp add mcp-biomodelling-servers -- uvx mcp-biomodelling-serversAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 18 |
|---|---|
| Package | mcp-biomodelling-servers |
| Transport | STDIO |
| Auth | None |
| Last updated | July 2, 2026 |
| Repository | marcorusc/mcp-biomodelling-servers ↗ |
What it does
Wire Boolean network simulation and attractor analysis into your coding agent for systems-biology or computational research workflows.
Who is it for?
Best when you're productizing computational biology agents that need MaBoSS-backed Boolean models.
Skip if: General SaaS apps with no network biology; teams unwilling to install Python/uvx biomodelling packages.
What you get
Your agent can invoke MaBoSS simulation and analysis steps with consistent parameters and traceable outputs in the same session as your code.
- Agent-callable MaBoSS simulation and attractor analysis runs
- Stdio MCP configuration for biomodelling workflows
By the numbers
- Server version 1.0.0
- Transport: stdio
- Package identifier: mcp-biomodelling-servers on PyPI
README.md
MCP Bio‑Modelling Servers
This repository centralizes Model Context Protocol (MCP) servers that wrap Python‑based mechanistic / systems biology modelling tools. Each subfolder contains a server.py entrypoint plus a README describing the specific tool interface.
Current servers (see their own READMEs & upstream docs):
| Tool | Folder | Upstream Documentation | MCP Registry |
|---|---|---|---|
| MaBoSS | MaBoSS/ |
https://github.com/colomoto/pyMaBoSS | io.github.marcorusc/MaBoSS |
| NeKo | NeKo/ |
https://github.com/sysbio-curie/Neko | io.github.marcorusc/NeKo |
| PhysiCell (settings wrapper) | PhysiCell/ |
https://github.com/marcorusc/PhysiCell_Settings | io.github.marcorusc/PhysiCell |
All servers are Python processes speaking MCP over stdio.
Installation
Option A — pip (recommended)
pip install mcp-biomodelling-servers
Then run any server directly:
mcp-neko-server
mcp-maboss-server
mcp-physicell-server
Option B — uvx (no install needed)
uvx --from mcp-biomodelling-servers mcp-neko-server
uvx --from mcp-biomodelling-servers mcp-maboss-server
uvx --from mcp-biomodelling-servers mcp-physicell-server
Option C — from source (Conda, full control)
Clone this repo and set up a Conda environment with all dependencies (see Environment Assumption below).
MCP Background
The Model Context Protocol standardizes how external tools expose tools and resources to AI assistants / IDEs. Spec & introduction: https://modelcontextprotocol.io/docs/getting-started/intro
Each server.py advertises modelling actions (e.g. run simulations, manage sessions) to any MCP‑aware client (e.g. VS Code with GitHub Copilot Chat MCP support).
Repository Layout
MaBoSS/ # MaBoSS MCP server (Boolean / stochastic models)
NeKo/ # NeKo MCP server
PhysiCell/ # PhysiCell settings / sessions MCP server
README.md
Consult the README within each tool folder for: purpose, required Python packages, and any model/data file expectations. Installation instructions for the modelling tools themselves live there (or in the upstream project links above) — they are intentionally not duplicated here.
Environment Assumption
All tools are Python‑based. Create (and manage) a single Conda environment that contains the dependencies for MaBoSS, NeKo, and PhysiCell. The exact creation commands are up to you (not prescribed here). Once created, note the absolute path to its Python interpreter (e.g. /home/you/miniforge3/envs/mcp_modelling/bin/python).
Configure in VS Code (GitHub Copilot Chat / MCP)
- Open VS Code and ensure the Copilot Chat (or other MCP-capable) extension is installed.
- Press
Ctrl + Shift + P→ "MCP: Open Configuration" (or edit~/.config/Code/User/mcp.jsondirectly). - Add entries for each server.
Simple setup (uvx / pip install)
If you installed via pip or want to use uvx, no paths are needed:
{
"servers": {
"neko": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "mcp-biomodelling-servers", "mcp-neko-server"]
},
"maboss": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "mcp-biomodelling-servers", "mcp-maboss-server"]
},
"physicell": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "mcp-biomodelling-servers", "mcp-physicell-server"]
}
}
}
Advanced setup (Conda environment, from source)
Use this if you need a custom Conda environment (e.g. for native MaBoSS binaries or local development):
{
"servers": {
"maboss": {
"type": "stdio",
"command": "/home/you/miniforge3/envs/mcp_modelling/bin/python",
"args": [
"/absolute/path/to/mcp-biomodelling-servers/MaBoSS/server.py"
],
"env": {
"PATH": "/home/you/miniforge3/envs/mcp_modelling/bin:${Path}",
"CONDA_PREFIX": "/home/you/miniforge3/envs/mcp_modelling"
}
},
"neko": {
"type": "stdio",
"command": "/home/you/miniforge3/envs/mcp_modelling/bin/python",
"args": [
"/absolute/path/to/mcp-biomodelling-servers/NeKo/server.py"
]
},
"physicell": {
"type": "stdio",
"command": "/home/you/miniforge3/envs/mcp_modelling/bin/python",
"args": [
"/absolute/path/to/mcp-biomodelling-servers/PhysiCell/server.py"
]
}
}
}
Replace /home/you/... and /absolute/path/to/... with your actual directories. Keep all three servers referencing the same Conda interpreter to share installed libraries.
After saving, reload / restart VS Code so the MCP client reconnects.
Activation / usage guidance in VS Code: https://code.visualstudio.com/docs/copilot/chat/mcp-servers
You should then see the servers' tools listed in the Copilot Chat "/tools" (or similar) UI. Invoke them by name with required parameters.
Adding Another Server
- Create a new folder with
server.pyand a README describing the underlying modelling tool and dependencies. - Follow existing server structure for registering MCP tools.
- Update your
mcp.jsonwith a new block (use the same Conda Python path). - Document any additional env vars in that folder README.
License
Project is MIT (see existing LICENSE file). Underlying tools retain their own licenses — consult upstream repositories.
Quick Reference
| Action | What to Do |
|---|---|
| Get tool install steps | Open the tool’s subfolder README or upstream link |
| Ensure deps present | Install into your chosen Conda env (user‑defined) |
| Configure MCP | Edit ~/.config/Code/User/mcp.json as above |
| Reload servers | Reload VS Code window |
| Learn MCP | Spec: modelcontextprotocol.io; VS Code guide link above |
Happy modelling!
Recommended MCP Servers
How it compares
Specialized biomodelling MCP integration, not a general spreadsheet or database server.
FAQ
Who is MaBoSS MCP for?
Developers and researchers using Claude Code or Cursor who model gene regulatory or signaling networks with MaBoSS and want those runs callable as MCP tools.
When should I use MaBoSS MCP?
Use it during build when you integrate simulation into an agent workflow—attractor searches, parameter sweeps, or reproducible network experiments—not for marketing or ops analytics.
How do I add MaBoSS to my agent?
Register a stdio MCP server with runtimeHint uvx, --from mcp-biomodelling-servers, and positional mcp-maboss-server per the server.json in the MaBoSS subfolder of mcp-biomodelling-servers.