Skip to main content

BindAI MCP

bindai-mcp provides MCP integration functionality for connecting BindAI applications and agents to external tool services.

The package exposes a small public API centered around MCPClient and MCPTool.

Current status: The package currently provides a lightweight HTTP-based tool discovery and invocation bridge. Full Model Context Protocol interoperability is part of the BindAI MCP roadmap.

Features

  • MCP integration foundation
  • Remote tool discovery
  • Representation of discovered tools as BindAI tools
  • Integration of external tools into BindAI applications
  • Lightweight public Python API
  • Separation between MCP integration and BindAI core functionality

Installation

bindai-mcp is part of the BindAI workspace.

From the BindAI repository root:

uv sync

The package can then be used through the workspace environment.

For public package installation, install the published bindai-mcp package from PyPI when the corresponding release is available.

Basic Usage

The public API can be imported as:

from bindai_mcp import MCPClient, MCPTool

MCPClient provides the client-side integration, while MCPTool represents a remotely exposed tool as a BindAI tool.

The current implementation uses an HTTP service exposing tool discovery and invocation endpoints.

A typical integration flow is:

BindAI Agent / Application
           │
           ▼
       MCPClient
           │
           ▼
     HTTP Tool Service
           │
      ┌────┴────┐
      ▼         ▼
   Tool A     Tool B

The current client expects:

GET  /tools
POST /call

The exact request and response behavior is provided by the package implementation.

Public API

MCPClient

MCPClient is the primary client interface for discovering external tools.

from bindai_mcp import MCPClient

Example:

client = MCPClient("http://localhost:8000")
tools = await client.list_tools()

MCPTool

MCPTool represents a remotely available tool using BindAI's tool abstraction.

from bindai_mcp import MCPTool

Discovered tools can be represented as BindAI tools and integrated with BindAI agent execution.

BindAI Integration

The MCP integration keeps external tool connectivity separate from BindAI's core execution and agent abstractions.

Conceptually:

                 BindAI
                    │
           ┌────────┴────────┐
           │                 │
         Agent          Application
           │                 │
           └────────┬────────┘
                    │
                MCPClient
                    │
                    ▼
             External Tool
               Service
                    │
              ┌─────┴─────┐
              ▼           ▼
           MCPTool     MCPTool

This separation allows the MCP integration layer to evolve independently from the BindAI core framework.

MCP Roadmap

The BindAI MCP package is intended to evolve toward full MCP protocol support.

Planned capabilities include:

  • Standard MCP client communication
  • MCP tool discovery
  • MCP tool invocation
  • MCP resource support where appropriate
  • BindAI agent integration
  • Authentication and configuration
  • MCP server integration where appropriate
  • Documentation and examples
  • Protocol-level interoperability testing

The current HTTP tool bridge should therefore be considered the foundation for the broader MCP integration rather than a complete MCP protocol implementation.

Development

From the repository root:

uv sync

Run the complete test suite:

uv run pytest

Run type checking for the package:

uv run mypy packages/bindai-mcp

Build the package:

uv build --package bindai-mcp

Package Structure

The package follows the standard BindAI package layout:

bindai-mcp/
├── pyproject.toml
├── README.md
├── src/
│   └── bindai_mcp/
│       ├── __init__.py
│       └── client.py
└── tests/
    └── test_client.py

API Stability

The package currently exposes:

from bindai_mcp import MCPClient, MCPTool

These are the intended public entry points of the package.

Internal implementation details should be treated as subject to change unless explicitly documented as public API.

Documentation

Full BindAI documentation is available at:

https://docs.bindai.dev

License

BindAI is released under the MIT License.

Release files for bindai-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bindai-mcp 0.1.0
File Size Uploaded
bindai_mcp-0.1.0.tar.gz 4.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for bindai-mcp 0.1.0
File Interpreter ABI Platform
bindai_mcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 8.0 kB

Release files / bindai_mcp-0.1.0.tar.gz

Download URL bindai_mcp-0.1.0.tar.gz
Size 4.3 kB
Tags Source
SHA-256 checksum
How to use checksums
52a57b4c1049abc93ed44684d822cca37a3b4c7d76ef811f8889885ee91b59f5
BLAKE2b-256 checksum
How to use checksums
0717bc5b5f0a1f3b229eb01297f2146b627b24ecb77757eaaeb313b7aeb7a99d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.2

Release files / bindai_mcp-0.1.0-py3-none-any.whl

Download URL bindai_mcp-0.1.0-py3-none-any.whl
Size 3.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f72d43b3d9b11b26eb5c18ac874231acda538202a276d5dadc7831a0716d9308
BLAKE2b-256 checksum
How to use checksums
78db3cbccc69b3481829c20b39dbe0d0564fbd5d2b5f830c7902cc051c597e7d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.2

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page