prodimopy-mcp
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
prodimopy-mcp
An MCP server for prodimopy, the Python package for the ProDiMo code. With this server, an AI agent can look up prodimopy functions, the prodimopy documentation and the example notebooks.
This is still experimental, but it should be safe to use. The server runs locally on your machine.
The server provides these tools:
Tool | Purpose |
| List the read and plot functions of prodimopy |
| Signature and docstring of a prodimopy function or method |
| Search the source code of the installed prodimopy |
| Search the prodimopy documentation |
| Find example notebooks and copy one to a directory |
| Check that the server runs |
The introspection tools use the prodimopy version that is installed together with prodimopy-mcp. The documentation and notebooks come from the prodimopy release given by prodimopy-ref in pyproject.toml.
Installation
pip install prodimopy-mcpThis also installs prodimopy. You then have the command prodimopy-mcp. To test it, run:
prodimopy-mcpIf there is no error message, the server works. Stop it with Ctrl+C.
This package replaces
pip install prodimopy[agent]. The command nameprodimopy-mcpis the same, so existing MCP client configurations keep working.
Related MCP server: Simple Code Review Assistant
Use with an AI client
How you add the server depends on your AI client. What you need is that the client can start prodimopy-mcp and talk to it over stdio.
In VS Code, add the server to .vscode/mcp.json in your project (see MCP servers in VS Code). For a conda environment called prodimopy:
{
"servers": {
"prodimopy-mcp-server": {
"type": "stdio",
"command": "conda",
"args": ["run", "--no-capture-output", "-n", "prodimopy", "prodimopy-mcp"]
}
}
}If you use the pixi environment of this repository, use "command": "pixi" and "args": ["run", "--manifest-path", "/path/to/prodimopy-mcp", "prodimopy-mcp"].
Then ask your agent something like "What plotting functionality does prodimopy provide?".
Development
The development environments are managed with pixi (see pyproject.toml):
pixi run sync-data # generate the documentation and notebook data (see below)
pixi run test # run the tests
pixi shell # shell in the default environmentDocumentation and notebook data
The server ships text versions of the prodimopy documentation and the example notebooks (without outputs) in src/prodimopy_mcp/data/. This data is generated, not tracked by git, but it is included in the sdist and the wheel.
scripts/sync_data.py clones prodimopy at the git ref in pyproject.toml:
[tool.prodimopy-mcp]
prodimopy-ref = "v2.8.0"Then it builds the prodimopy documentation with Sphinx, converts the pages to text and copies the notebooks. There are two sources:
Task | Source |
| local prodimopy repository: |
|
Both give the same result. The local variant clones the committed state of the ref from your repository; it does not change your working tree or branch, and uncommitted changes are not included. If the tag is missing locally, run git fetch --tags in the prodimopy repository.
For development you can use another branch or tag: pixi run sync-data --ref master.
After a new prodimopy release:
Set
prodimopy-refto the new tag.Run
pixi update prodimopy, so that the installed prodimopy matches the tag (sync-datawarns if it does not).Release a new prodimopy-mcp version.
Release
pixi run release-build # check clean tree, sync data, tests, build, twine check, data check
pixi run upload-testpypi # upload dist/* to TestPyPI
pixi run upload-pypi # upload dist/* to PyPIThe version comes from the git tags (setuptools-scm). release-build stops if the working tree has uncommitted changes. scripts/check_dist.py makes sure that the sdist and the wheel contain the generated data. The upload tasks ask for the API token (input is hidden).
License
MIT, see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Access Pollinations models and API capabilities through agent tools.
GitHub, npm, PyPI, Stack Overflow, arXiv and OpenAlex paper search as agent tools.
Search @imqueue docs and scaffold typed services & clients from your AI coding agent.
Connect AI agents to ProductNow's context engine to search, create, review, and act.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides real-time access to Python package documentation, source code, and symbol search to prevent AI hallucinations.710 PyPI7MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models to fetch GitHub repository information, read file contents, and search local documentation.-
- AlicenseNot gradedqualityCmaintenanceProvides coding agents with read-only MCP tools to search Python repositories, retrieve size-bounded cited source context, analyze dependency impact, and check index status—all via local incremental AST indexing and BM25 retrieval.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to discover and invoke tools for saving and retrieving code snippets, generating style guides and wiki documentation, and orchestrating multi-agent documentation workflows with semantic search.-