Generate Agent Integration Kits for existing systems with AI-powered dynamic generation via Claude Agent SDK.
Project description
AgentBridge uses an AI analysis agent to understand your project code, then generates a complete Agent Integration Kit that works with MCP, Claude, OpenAI, and Vercel AI SDK out of the box.
Deterministic scanners still collect candidate evidence from OpenAPI, GraphQL, SQL, and source routes, but they are not the source of truth. The AI agent reads the project context, reasons about business objects and side effects, then creates tools, skills, prompts, guardrails, tests, and protocol metadata.
๐ Table of Contents
- โจ Features
- ๐ Quick Start
- ๐ CLI Reference
- ๐ How AgentBridge Analyzes Projects
- ๐ Candidate Evidence Sources
- ๐ Stable Kit Protocol
- ๐ค AI Agent Generation
- ๐ก๏ธ Safety Model
- ๐๏ธ Architecture
- ๐ Documentation
- ๐งฉ Extending AgentBridge
- ๐ฆ Publishing & Installation
- ๐ค Contributing
- ๐ License
โจ Features
|
๐ AI-first code analysis Uses an AI agent to interpret business objects, workflows, permissions, and side effects from project code |
๐ง Multi-format Generation Outputs MCP, Claude, OpenAI, and Vercel AI SDK tool definitions simultaneously |
|
๐ค AI-Powered Generation Uses Claude Agent SDK (primary) or Anthropic API (fallback) to dynamically generate tools, skills, and prompts |
๐ง Agent as a Service Runs as an interactive agent for your existing project via Claude Agent SDK |
|
๐ก๏ธ Safety-first Classifies operations by risk level with human-in-the-loop confirmation for dangerous actions |
๐งช Dry-run Validation Test tool invocations against generated guardrails before executing |
|
๐ Custom LLM Providers Supports DeepSeek, OpenRouter, and any Anthropic-compatible endpoint |
๐ชถ Rules as evidence OpenAPI, GraphQL, SQL, and route scanners provide candidate signals for the AI agent to verify or override |
๐ Quick Start
Installation
pip install agbr
๐ฆ Install with optional features
# AI-powered generation + agent sessions (recommended)
pip install "agbr[agent]"
# Lightweight AI generation (no Claude Agent SDK)
pip install "agbr[ai]"
# Everything
pip install "agbr[all]"
# Install from source (for development)
git clone git@github.com:jastfkjg/AgentBridge.git
cd AgentBridge
pip install -e ".[all]"
Configure LLM Provider
AgentBridge relies on an AI backend for existing-project understanding. Deterministic scanners and regex/rule signals are used as evidence for the AI agent, not as the final project model. The schema-only OpenAPI-to-MCP path can run with --no-ai; directory-level project analysis should use Claude Agent SDK or another Anthropic-compatible provider.
# Required for project directory analysis
export ANTHROPIC_API_KEY="sk-ant-..."
# Optional: Custom API endpoint
export ANTHROPIC_BASE_URL="https://api.deepseek.com/anthropic" # DeepSeek
# export ANTHROPIC_BASE_URL="https://openrouter.ai/api/v1" # OpenRouter
# Optional: Custom model name
export ANTHROPIC_MODEL="deepseek-v4-flash"
๐ Or pass via CLI flags
agentbridge generate examples/writing_system --output build/kit \
--api-key "sk-..." \
--base-url "https://api.deepseek.com/anthropic" \
--model "deepseek-v4-flash"
Note: When
ANTHROPIC_BASE_URLis set, AgentBridge automatically uses theanthropicSDK backend (notclaude-agent-sdk) for generation, since custom endpoints are not supported by the agent SDK.
Generate an Agent Integration Kit
# Project directory analysis uses AI. Generated files are written only to --output.
agentbridge generate examples/writing_system --output .agentbridge/writing-kit
Run an MCP Server from OpenAPI
agentbridge generate openapi.json --output .agentbridge/openapi-kit --no-ai
# Dry-run by default, with no target-system side effects
agentbridge serve .agentbridge/openapi-kit
# Execute real HTTP calls against the target system
agentbridge serve .agentbridge/openapi-kit \
--base-url http://localhost:8080 \
--bearer-env API_TOKEN \
--execute
Generate MCP client snippets for Claude Desktop, Claude Code, Codex CLI, or generic stdio clients:
agentbridge mcp-config .agentbridge/openapi-kit \
--base-url http://localhost:8080 \
--bearer-env API_TOKEN \
--execute
Run as an Agent
agentbridge chat .agentbridge/writing-kit
# Browser chat UI
agentbridge web .agentbridge/writing-kit --port 8765
Run Tests
PYTHONPATH=src python -m unittest discover -s tests
๐ CLI Reference
| Command | Description |
|---|---|
agentbridge discover <paths> |
Discover and print capabilities as JSON |
agentbridge init <paths> -o <dir> |
Generate, validate, and print next steps for a new kit |
agentbridge generate <paths> -o <dir> |
Generate an Agent Integration Kit; uses AI enhancement when configured |
agentbridge validate <kit> |
Validate kit protocol, guardrails, transports, and secret hygiene |
agentbridge doctor <kit> |
Diagnose kit readiness for dry-run or execution mode |
agentbridge mcp-config <kit> |
Print or write Claude/Codex/generic MCP client snippets |
agentbridge serve <kit> |
Run a generated kit as a stdio MCP Server |
agentbridge dry-run <kit> <tool> |
Dry-run a tool invocation |
agentbridge chat <kit> |
Start an interactive CLI chat over the kit runtime |
agentbridge web <kit> |
Start a browser chat UI over the kit runtime |
๐ Full command details
discover
agentbridge discover examples/writing_system
generate
agentbridge init examples/writing_system/openapi.json --output build/openapi-kit --no-ai
agentbridge generate examples/writing_system --output build/agent-kit
# No LLM, useful for schema-only OpenAPI-to-MCP Server kits
agentbridge generate examples/writing_system/openapi.json --output build/openapi-kit --no-ai
# With custom name
agentbridge generate examples/writing_system --output build/agent-kit --name my-kit
# With custom LLM provider
agentbridge generate examples/writing_system --output build/agent-kit \
--api-key "sk-..." --base-url "https://api.deepseek.com/anthropic" --model "deepseek-v4-flash"
dry-run
# Normal invocation
agentbridge dry-run build/agent-kit create_chapter --args '{"project_id":"p1","title":"Opening"}'
# High-risk operation (requires confirmation)
agentbridge dry-run build/agent-kit delete_character \
--args '{"project_id":"p1","character_id":"c1"}' --confirmed
validate and doctor
agentbridge validate build/agent-kit
agentbridge doctor build/agent-kit --execute --base-url http://localhost:8080
serve
# stdio MCP Server, dry-run by default
agentbridge serve build/openapi-kit
# Execute real HTTP calls against the target system
agentbridge serve build/openapi-kit \
--base-url http://localhost:8080 \
--header "X-Tenant=demo" \
--bearer-env API_TOKEN \
--execute \
--audit-log .agentbridge/audit.jsonl
# Conservative runtime policy
agentbridge serve build/openapi-kit --read-only
agentbridge serve build/openapi-kit --deny-risk destructive --deny-risk external_side_effect
chat
agentbridge chat build/agent-kit
# Execute real HTTP calls, with session memory
agentbridge chat build/agent-kit \
--base-url http://localhost:8080 \
--bearer-env API_TOKEN \
--execute \
--audit-log .agentbridge/audit.jsonl \
--user alice \
--session demo
Inside chat, use /tools, /run <tool> key=value, confirm, cancel, and /history.
web
agentbridge web build/agent-kit --port 8765
# Execute real HTTP calls in the Web UI
agentbridge web build/agent-kit \
--base-url http://localhost:8080 \
--bearer-env API_TOKEN \
--execute \
--read-only
mcp-config
agentbridge mcp-config build/openapi-kit \
--base-url http://localhost:8080 \
--bearer-env API_TOKEN \
--execute
# Write snippets back into the kit
agentbridge mcp-config build/openapi-kit --write
๐ How AgentBridge Analyzes Projects
AgentBridge is designed so the AI agent performs the main project understanding step. Rule-based discovery is intentionally conservative and acts as evidence collection.
| Stage | Role |
|---|---|
| Candidate scanning | Extract OpenAPI operations, GraphQL fields, SQL tables, and route handlers |
| AI project analysis | Infer business objects, workflows, permission boundaries, side effects, missing operations, and assumptions |
| Capability normalization | Convert the AI-enhanced analysis into stable tool-ready capabilities |
| Kit generation | Emit tools, skills, prompts, resource schemas, guardrails, dry-run plans, and tests |
AgentBridge does not modify the target project during discovery or generation. All generated artifacts are written under the caller-provided output directory, preferably outside the project or under a dedicated ignored directory such as .agentbridge/.
The generated kit preserves both layers:
analysis/rule_signals.json: deterministic candidate evidenceanalysis/agent_analysis.json: AI agent project analysis and reasoning
๐ Candidate Evidence Sources
| Source Type | Formats |
|---|---|
| ๐ API Schemas | OpenAPI JSON/YAML, GraphQL schemas |
| ๐๏ธ Database Schemas | SQL CREATE TABLE statements |
| ๐ Python Routes | FastAPI @router.get/post/..., Flask @app.route |
| ๐ JavaScript Routes | Express app.get/post/... |
| โ Java Routes | Spring @GetMapping/@PostMapping/... |
All sources are normalized into a common capability model with:
| Field | Description |
|---|---|
domain + resource |
Logical grouping |
action |
What the capability does |
input_schema |
JSON Schema parameters |
risk |
read / write / destructive / external_side_effect |
confirm_required |
Whether human approval is needed |
source |
Full traceability back to the origin file |
๐ Stable Kit Protocol
Current protocol: agentbridge-kit/v1. See docs/kit-protocol.md.
agent-kit/
โโโ manifest.json # Kit metadata and summary
โโโ capabilities.json # AI-enhanced normalized capabilities
โโโ analysis/
โ โโโ rule_signals.json # Scanner evidence used as AI context
โ โโโ agent_analysis.json # AI project analysis and risk reasoning
โโโ spec/
โ โโโ kit-protocol.md # Protocol contract copied into the kit
โโโ tools/
โ โโโ mcp_tools.json # MCP tool definitions
โ โโโ openai_tools.json # OpenAI function calling format
โ โโโ claude_tools.json # Claude tool use format
โ โโโ vercel_ai_tools.ts # Vercel AI SDK TypeScript tools
โโโ skills/
โ โโโ writing.md # Domain-specific skill definitions
โโโ prompts/
โ โโโ system.md # Agent system prompt
โโโ resources/
โ โโโ schema.json # Resource schema summary
โโโ guardrails/
โ โโโ permissions.json # Risk policy and confirmation rules
โโโ tests/
โ โโโ tool_invocation_tests.json # Auto-generated invocation tests
โ โโโ test_generated_tools.py # Python unit tests for tool contracts
โโโ clients/
โ โโโ mcp-client-configs.json # Claude/Codex/generic MCP config snippets
โ โโโ README.md # Client setup notes
โโโ dry_run_plan.json # Dry-run execution plan
๐ค AI Agent Generation
AgentBridge uses an AI analysis agent to generate the semantic parts of the kit: project analysis, tool descriptions, skills, system prompts, risk assessments, and inferred tools. Rule-based analysis is passed to the agent as candidate evidence and safety hints, not copied directly as final output.
| What | Description |
|---|---|
| ๐งญ Project analysis | Business objects, workflows, permission boundaries, side effects, and assumptions |
| ๐ Enhanced tool descriptions | Context-aware descriptions that capture business semantics |
| ๐ฏ Domain-specific skills | Workflow prompts tailored to your domain with best practices |
| ๐ง Intelligent system prompts | Prompts that understand resource relationships and suggest safe sequences |
| ๐ Inferred additional tools | Tools implied by your schema but not explicitly present |
| โ ๏ธ Improved risk assessments | LLM evaluates risk with rule-based hints as context |
AI Backend
| Backend | Package | Use Case |
|---|---|---|
| Claude Agent SDK (primary) | claude-agent-sdk |
Generation + interactive agent sessions |
| Anthropic API (fallback) | anthropic |
Generation only, supports custom endpoints |
When claude-agent-sdk is installed and no custom ANTHROPIC_BASE_URL is set, it is used automatically. When a custom endpoint is configured or claude-agent-sdk is not installed, the anthropic SDK is used.
Programmatic Usage
from pathlib import Path
from agentbridge.generator import AgentKitGenerator
from agentbridge.agent import AIGenerator, AgentRunner
# Generate with default provider (Anthropic Claude)
ai = AIGenerator(api_key="sk-ant-...")
kit = AgentKitGenerator(ai_generator=ai).generate(
[Path("examples/writing_system")],
Path("build/agent-kit"),
)
# Custom LLM provider (e.g., DeepSeek)
ai = AIGenerator(
api_key="sk-d831ecabc21842fdae6f30c24dd3b052",
base_url="https://api.deepseek.com/anthropic",
model="deepseek-v4-flash",
)
# Agent session
import asyncio
async def main():
runner = AgentRunner(kit_dir="build/agent-kit", api_key="sk-ant-...")
async for message in runner.query("List all chapters in project p1"):
print(message)
asyncio.run(main())
๐ก๏ธ Safety Model
| Risk Level | Confirmation | Examples |
|---|---|---|
๐ข read |
Not required | GET, list, search, find |
๐ก write |
Optional by policy | POST, create, update, rewrite |
๐ด destructive |
Required | DELETE, remove, destroy, drop, cancel |
๐ external_side_effect |
Required | publish, send, email, pay, deploy, export |
The safety model is applied consistently. Rule-based risk classification provides initial context, and the LLM may override when justified.
๐๏ธ Architecture
โโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโ
โ Rule Signals โโโโโโถโ AI Analysis โโโโโโถโ Kit Generator โ
โ (schemas, โ โ Agent โ โ (protocol v1) โ
โ routes, SQL)โ โ โ โ โ
โโโโโโโโโโโโโโโ โโโโโโโโฌโโโโโโโ โโโโโโโโโโฌโโโโโโโโโ
โ โ
โโโโโโโโผโโโโโโโ โโโโโโโโผโโโโโโโโโ
โ Capabilitiesโ โ Agent Runtime โ
โ Skills โ โ Dry-run + โ
โ Guardrails โ โ Guardrails โ
โโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโ
๐ Documentation
- Architecture
- Kit protocol
- OpenAPI to MCP Server
- Chat entrypoints
- TODO / Roadmap
- ไธญๆ README
- ไธญๆๆถๆ่ฏดๆ
- ไธญๆๅฅไปถๅ่ฎฎ
- ไธญๆ OpenAPI ๅฐ MCP Server
- ไธญๆ่ๅคฉๅ ฅๅฃ
๐งฉ Extending AgentBridge
| Extension | How |
|---|---|
| New schema parser | Implement a discoverer in discovery.py |
| New tool format | Add a builder function in generator.py |
| Custom AI prompts | Override prompts in agent.py |
| Custom risk policy | Modify policy.py |
| Custom agent tools | Extend AgentRunner._build_kit_tools() |
๐ฆ Publishing & Installation
๐ง How does `pip install "agbr"` work?
AgentBridge is packaged as a standard Python package using pyproject.toml + setuptools. Here's the mechanism:
1. Package Structure
AgentBridge/
โโโ pyproject.toml # Package metadata, dependencies, entry points
โโโ src/
โ โโโ agentbridge/ # Actual Python package
โ โโโ __init__.py
โ โโโ cli.py # CLI entry point
โ โโโ agent.py
โ โโโ generator.py
โ โโโ ...
โโโ tests/
2. pyproject.toml Key Sections
[project]
name = "agbr" # pip install agbr
version = "0.2.0"
[project.optional-dependencies] # pip install "agbr[agent]"
agent = ["claude-agent-sdk>=0.1.0"]
ai = ["anthropic>=0.30.0"]
[project.scripts]
agentbridge = "agentbridge.cli:main" # CLI entry point
[tool.setuptools.packages.find]
where = ["src"] # Code lives in src/
3. How pip install Works
- Build:
pipreadspyproject.toml, usessetuptoolsto build a wheel (.whl) - Install: The wheel is installed into your Python environment's
site-packages/ - CLI: The
[project.scripts]section creates aagentbridgeexecutable in your PATH that callsagentbridge.cli:main
4. Publishing to PyPI (so anyone can pip install)
# Build the package
pip install build
python -m build
# Upload to TestPyPI (for testing)
pip install twine
twine upload --repository testpypi dist/*
# Upload to PyPI (for real)
twine upload dist/*
After publishing, anyone can run pip install "agbr".
5. Installing Without PyPI
Until the package is published on PyPI, users can install it in these ways:
# Install from local source (editable mode, for development)
pip install -e .
# Install from GitHub repository
pip install git+ssh://git@github.com/jastfkjg/AgentBridge.git
# Install from a local wheel
pip install dist/agentbridge-0.2.0-py3-none-any.whl
๐ค Contributing
Contributions are welcome! Here's how you can help:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Please make sure tests pass:
PYTHONPATH=src python -m unittest discover -s tests -v
๐ License
This project is licensed under the MIT License โ see the LICENSE file for details.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file agbr-0.4.0.tar.gz.
File metadata
- Download URL: agbr-0.4.0.tar.gz
- Upload date:
- Size: 75.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
d2e50146b6b056973b61ec7f74d9523862e35c63cb93c3908e57e17fbafcc719
|
|
| MD5 |
7e4227417192ff4e1add8e81c7f063b9
|
|
| BLAKE2b-256 |
705aabb9c8cf706a0e2c7df867150d620b94265165202b2a19bde02870d762fc
|
File details
Details for the file agbr-0.4.0-py3-none-any.whl.
File metadata
- Download URL: agbr-0.4.0-py3-none-any.whl
- Upload date:
- Size: 54.1 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a84d9b03ed25eb30303e8df832c2ebd2f04aa3b8432c3c60ae0aba44884b4539
|
|
| MD5 |
0ce91859d379344f5fd8cc59808a1401
|
|
| BLAKE2b-256 |
3fd2512f61215bf91703d1c3389453e5fb6857999317b69ea6fa75cf50d834d0
|