Integrum - Reflection based MCP server from any Python Module/Library [P]

Reddit r/MachineLearning Tools

Summary

Integrum is an open-source (MIT) Python library and CLI that uses reflection to automatically generate MCP servers from any existing Python module or library, demonstrated by giving Gemma access to scikit-learn for building a random forest classifier.

Hi! I wrote a small library called Integrum that allows you to quickly create MCP server(s) from existing Python libraries or modules. It has a CLI so it is really easy to use (I hope!). It is open-source (MIT) and on PyPI, so sharing it here if somebody finds it useful. Code: https://github.com/alphadeepai/integrum Blog post: https://nmilosev.svbtle.com/integrum-reflection-based-mcp-server-from-any-python-module-or-library As an example I gave Gemma 4 access to scikit-learn and told it to create a RF classifier for a toy dataset (Iris) and it did it rather well! Here is that example session.. Obviously an interesting discussion is this approach vs. just letting the agents write code: I think this approach is more formal and therefore easier to verify. I haven't found any other reflection based approaches like this, let me know if I missed some.
Original Article

Similar Articles

MCPJam

Product Hunt

MCPJam is a testing and evaluation platform for MCP servers, enabling user testing and CI/CD integration for ChatGPT, Claude, and Copilot via desktop app, CLI, or SDK.

PrefectHQ/fastmcp

GitHub Trending (daily)

FastMCP is a Python framework by Prefect for building MCP servers, clients, and apps, simplifying the connection of LLMs to tools and data.

API to MCP

Product Hunt

API to MCP lets you turn any API into an MCP server for AI agents, enabling seamless integration.

Open Source Project to help Secure LLM powered Applications

Reddit r/artificial

Sente Labs open-sourced extensible-mcp, an MCP proxy that dynamically loads MCP servers without polluting the LLM context while enforcing zero-trust policy controls (Rego, CEL, and now Cedar) over tool calls. Tool definitions live in a queryable vector store, and policies and credentials are kept outside the LLM's reach, distinguishing user intent from granted rights.