
NeKo Biological Network Builder
- 18 repo stars
- Updated July 2, 2026
- marcorusc/mcp-biomodelling-servers
NeKo is an MCP server that constructs and analyzes biological networks from pathway databases via agent tools.
About
NeKo Biological Network Developer is an MCP server that lets coding agents construct and analyze biological networks using pathway databases through the NeKo stack. developers shipping research copilots, pathway visualization products, or internal bioinformatics tooling use it to keep network builds inside the same agent session as application code. Configuration follows the mcp-biomodelling-servers pattern: uvx, --from mcp-biomodelling-servers, and mcp-neko-server. Reach for it when you are prototyping knowledge-graph features, standardizing pathway imports, or automating network QC before downstream simulation with sibling servers like MaBoSS or PhysiCell. It assumes comfort with pathway semantics and Python tooling. The server accelerates integration; it does not validate biological conclusions or replace curator review of database releases.
- Biological network construction from pathway database sources
- Network analysis workflows exposed as MCP tools
- Stdio MCP via uvx mcp-biomodelling-servers
- Entry point mcp-neko-server in the NeKo repo subfolder
- Version 1.0.0 aligned with MCP server schema 2025-12-11
NeKo Biological Network Builder 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
Let your agent build and analyze biological networks from pathway databases without hand-curating every edge in scripts.
Who is it for?
Best when you're creating agent-assisted pathway or network-graph features grounded in public pathway databases.
Skip if: Apps with no life-sciences data model; teams that only need generic SQL or CSV analytics.
What you get
Your agent can request NeKo-backed network build and analysis steps with repeatable MCP calls alongside your repo work.
- MCP-driven biological network construction and analysis
- Stdio config for NeKo in agent MCP settings
By the numbers
- Server version 1.0.0
- Transport: stdio
- Runtime entry: mcp-neko-server
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
Pathway-network construction MCP, not a Boolean simulator or spreadsheet SQL server.
FAQ
Who is NeKo MCP for?
Developers and small teams using Claude Code or Cursor to automate biological network construction from pathway databases in research or biotech tooling.
When should I use NeKo MCP?
Use it in the build phase while integrating pathway-derived networks into agents, APIs, or analysis pipelines before you ship end-user features.
How do I add NeKo to my agent?
Add a stdio server with uvx, --from mcp-biomodelling-servers, and positional mcp-neko-server as defined in server.json for io.github.marcorusc/NeKo.