Turn any Python library or your local script into an LLM Tool in seconds.
AllBeAPI is a high-performance bridge that instantly exposes any Python environment—whether standard PyPI libraries or your own custom code—as a Model Context Protocol (MCP) server. It enables Large Language Models (Claude, ChatGPT, etc.) to execute local functions, manipulate dataframes, manage stateful objects, and interact with your system safely and efficiently.
Built on the latest StreamableHTTP protocol for maximum compatibility with Claude Desktop, LangChain, and Cursor.
Installation
pip install allbeapi
Usage Scenarios
AllBeAPI supports two primary use cases: exposing public libraries and exposing your own custom business logic.
1. Exposing Public Libraries
Expose pandas, numpy, or any other installed library to your LLM with a single command. AllBeAPI handles dependency installation and API generation automatically.
# Install, generate, and serve in one go
allbeapi start pandas
2. Exposing Custom Code
AllBeAPI treats your local Python scripts as first-class citizens. It parses type hints, docstrings, and class structures to generate high-quality tool definitions.
Step 1: Create your script (e.g., my_tools.py)
# my_tools.py
from typing import List
def calculate_bmi(weight_kg: float, height_m: float) -> float:
"""
Calculate Body Mass Index (BMI).
Args:
weight_kg: Weight in kilograms.
height_m: Height in meters.
"""
return round(weight_kg / (height_m ** 2), 2)
class BankAccount:
"""A stateful class example."""
def __init__(self, owner: str):
self.owner = owner
self.balance = 0
def deposit(self, amount: float) -> str:
self.balance += amount
return f"Deposited ${amount}. New balance: ${self.balance}"
# Factory function to create instances
def open_account(owner: str) -> BankAccount:
return BankAccount(owner)
Step 2: Start the server
# AllBeAPI detects the file in your current directory
allbeapi start my_tools
The LLM can now call calculate_bmi directly. Furthermore, if the LLM calls open_account, AllBeAPI automatically manages the returned BankAccount instance, allowing the LLM to make subsequent calls to deposit on that specific object.
Client Configuration
To use your tools with Claude Desktop or other MCP clients, add the corresponding configuration to your claude_desktop_config.json.
For a Library (e.g., pandas):
{
"mcpServers": {
"pandas": {
"command": "uv",
"args": ["run", "allbeapi", "start", "pandas"]
}
}
}
For Custom Code (e.g., my_tools):
{
"mcpServers": {
"my_tools": {
"command": "uv",
"args": ["run", "allbeapi", "start", "my_tools"],
"cwd": "/absolute/path/to/your/script/directory"
}
}
}
Key Features
Zero-Config Introspection
Automatically inspects Python packages or local modules, extracts public APIs, and generates a fully compliant MCP server. No manual schema definition (YAML/JSON) is required.
Stateful Object Management
Unlike standard stateless tools, AllBeAPI supports object-oriented workflows:
- Instance Persistence: When a function returns a class instance, it is stored in memory.
- Method Chaining: LLMs can invoke methods on specific stored instances via a generated
object_id. - Ideal For: Database connections, game states, simulation environments, and session-based workflows.
Smart Serialization Engine
LLMs struggle with complex objects. AllBeAPI handles them automatically:
- DataFrames: Converted to markdown or JSON previews based on size.
- Images: Automatically encoded or saved to temporary storage with resource links.
- Iterators: Automatically consumed and summarized.
Local & Secure
Runs entirely on your machine. No data leaves your network. You control the host binding (default 127.0.0.1) and execution environment.
Advanced Usage
Inspect a Library
Check which functions will be exposed and view their quality scores before generating code:
allbeapi inspect numpy
Generate Only
Generate the server code without running it (useful for auditing or customization):
allbeapi generate matplotlib --output-dir ./my-server
License
This project is licensed under the AGPL v3 License.
Metadata
Release files for allbeapi 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| allbeapi-1.1.0.tar.gz | 60.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| allbeapi-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 121.1 kB
Release files / allbeapi-1.1.0.tar.gz
| Download URL | allbeapi-1.1.0.tar.gz |
|---|---|
| Size | 60.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc942dd3107dbc8ce80fed719c41ee6ca12bc1b6fbbdae9bdbe7d37c17d70a82
|
|
BLAKE2b-256 checksum How to use checksums |
358ee4f0e37bc4e7de38cd81f2e2eae41dab1df90f8318ff7a46647d651983fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.
Transparency logRelease files / allbeapi-1.1.0-py3-none-any.whl
| Download URL | allbeapi-1.1.0-py3-none-any.whl |
|---|---|
| Size | 60.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a9f7e54011af296925181082bc1b77b91a5b7ac544e815389189b1e56a30a94
|
|
BLAKE2b-256 checksum How to use checksums |
7ffb9d85e9ed085284eec0edea98fe71cff51806e4ab89d1cf15a90a0e882e54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.
Transparency logSecurity for allbeapi 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for allbeapi-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.