Labsco
BrunoV21 logo

AiCore Project

โ˜… 27

from BrunoV21

A unified framework for integrating various language models and embedding providers to generate text completions and embeddings.

๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedPaid serviceNeeds API keys

AiCore Project

PyPI Downloads

โœจ AiCore is a comprehensive framework for integrating various language models and embedding providers with a unified interface. It supports both synchronous and asynchronous operations for generating text completions and embeddings, featuring:

๐Ÿ”Œ Multi-provider support: OpenAI, Mistral, Groq, Gemini, NVIDIA, and more ๐Ÿค– Reasoning augmentation: Enhance traditional LLMs with reasoning capabilities ๐Ÿ“Š Observability: Built-in monitoring and analytics ๐Ÿ’ฐ Token tracking: Detailed usage metrics and cost tracking โšก Flexible deployment: Chainlit, FastAPI, and standalone script support ๐Ÿ› ๏ธ MCP Integration: Connect to Model Control Protocol servers via tool calling ๐Ÿ–ฅ๏ธ Claude Code provider: Use your Claude subscription locally or remotely via the Claude Agents Python SDK โ€” no API key required

Key Features

Multi-provider Support

LLM Providers:

  • Anthropic
  • OpenAI
  • Mistral
  • Groq
  • Gemini
  • NVIDIA
  • OpenRouter
  • DeepSeek
  • Claude Code (local โ€” via Claude Agents Python SDK, no API key required)
  • Remote Claude Code (remote โ€” connects to a aicore-proxy-server over HTTP)

Embedding Providers:

  • OpenAI
  • Mistral
  • Groq
  • Gemini
  • NVIDIA

Observability Tools:

  • Operation tracking and metrics collection
  • Interactive dashboard for visualization
  • Token usage and latency monitoring
  • Cost tracking

MCP Integration:

  • Connect to multiple MCP servers simultaneously
  • Automatic tool discovery and calling
  • Support for WebSocket, SSE, and stdio transports

To configure the application for testing, you need to set up a config.yml file with the necessary API keys and model names for each provider you intend to use. The CONFIG_PATH environment variable should point to the location of this file. Here's an example of how to set up the config.yml file:

# config.yml
embeddings:
  provider: "openai" # or "mistral", "groq", "gemini", "nvidia"
  api_key: "your_openai_api_key"
  model: "text-embedding-3-small" # Optional

llm:
  provider: "openai" # or "mistral", "groq", "gemini", "nvidia"
  api_key: "your_openai_api_key"
  model: "gpt-o4" # Optional
  temperature: 0.1
  max_tokens: 1028
  reasonning_effort: "high"
  mcp_config: "./mcp_config.json" # Path to MCP configuration
  max_tool_calls_per_response: 3 # Optional limit on tool calls

config examples for the multiple providers are included in the config dir

MCP Integration Example

from aicore.llm import Llm
from aicore.config import Config
import asyncio

async def main():
    # Load configuration with MCP settings
    config = Config.from_yaml("./config/config_example_mcp.yml")
    
    # Initialize LLM with MCP capabilities
    llm = Llm.from_config(config.llm)
    
    # Make async request that can use MCP-connected tools
    response = await llm.acomplete(
        "Search for latest news about AI advancements",
        system_prompt="Use available tools to gather information"
    )
    print(response)

asyncio.run(main())

Example MCP configuration (mcp_config.json):

{
  "mcpServers": {
    "search-server": {
      "transport_type": "ws",
      "url": "ws://localhost:8080",
      "description": "WebSocket server for search functionality"
    },
    "data-server": {
      "transport_type": "stdio",
      "command": "python",
      "args": ["data_server.py"],
      "description": "Local data processing server"
    },
    "brave-search": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-brave-search"
      ],
      "env": {
        "BRAVE_API_KEY": "SUPER-SECRET-BRAVE-SEARCH-API-KEY"
      }
    }
  }
}

Claude Code Provider

AiCore supports routing completions through your Claude subscription via the Claude Agents Python SDK. No Anthropic API key is required โ€” auth is handled entirely by the Claude Code CLI. This is exposed through two providers and an optional proxy server:

ComponentDescription
claude_codeLocal provider โ€” runs the Claude Code CLI on the same machine as AiCore
remote_claude_codeRemote provider โ€” connects over HTTP to a aicore-proxy-server instance
aicore-proxy-serverProxy server โ€” wraps the local CLI as a FastAPI SSE service, shareable over a network

Both providers share the same acomplete() / complete() interface and emit identical tool-call streaming events โ€” you can switch between them with a single config change.


Local Provider (claude_code)

Runs claude-agent-sdk directly on the machine where AiCore is executing.

Prerequisites

# 1. Install the Claude Code CLI (requires Node.js 18+)
npm install -g @anthropic-ai/claude-code

# 2. Authenticate once
claude login

# 3. Install AiCore (the Python SDK is included automatically)
pip install core-for-ai

Quickstart

from aicore.llm import Llm
from aicore.llm.config import LlmConfig

config = LlmConfig(
    provider="claude_code",
    model="claude-sonnet-4-5-20250929",
    # No api_key needed โ€” auth is handled by the CLI
)

llm = Llm.from_config(config)
response = await llm.acomplete("List all Python files in this project")
print(response)

Config File

# config/config_example_claude_code.yml
llm:
  provider: "claude_code"
  model: "claude-sonnet-4-5-20250929"

  # Optional
  permission_mode: "bypassPermissions"   # default โ€” all tools allowed
  cwd: "/path/to/your/project"           # working directory for the CLI
  max_turns: 10                           # limit agentic turns
  mcp_config: "./mcp_config.json"   # pass through an MCP config file
  cli_path: "/usr/local/bin/claude"      # override if CLI is not on PATH
  allowed_tools:
    - "Read"
    - "Write"
    - "Bash"

Proxy Server (aicore-proxy-server)

The proxy server wraps claude-agent-sdk in a FastAPI SSE service so Claude Code can be accessed remotely over HTTP. Useful when:

  • The Claude Code CLI is authenticated on a different machine (e.g. a dev box, a server, or WSL)
  • You want to share a single Claude subscription across multiple AiCore clients
  • Your AiCore workload runs in a container or cloud environment that cannot run the CLI directly

Installation (server-side only)

# Install AiCore with the claude-server extras
pip install core-for-ai[claude-server]

# Also install the Claude Code CLI and authenticate
npm install -g @anthropic-ai/claude-code
claude login

The [claude-server] extra installs fastapi, uvicorn[standard], and python-dotenv. pyngrok is optional and only needed for the ngrok tunnel mode.

Starting the Server

# Minimal โ€” binds to 127.0.0.1:8080, prompts for tunnel choice interactively
aicore-proxy-server

# Fully configured
aicore-proxy-server \
  --host 0.0.0.0 \
  --port 8080 \
  --token my-secret-token \
  --tunnel none \
  --cwd /path/to/project \
  --log-level INFO

# Or via Python module
python -m aicore.scripts.claude_code_proxy_server --port 8080 --tunnel none

On first run the bearer token is auto-generated and printed. Set CLAUDE_PROXY_TOKEN in your environment or .env file to reuse it across restarts, or pass --token explicitly.

CLI Reference

FlagDefaultDescription
--host127.0.0.1Bind address
--port8080TCP port
--token(auto-generated)Bearer token; also reads CLAUDE_PROXY_TOKEN env var
--tunnel(prompt)none / ngrok / cloudflare / ssh
--tunnel-portsame as --portRemote port for SSH tunnels
--cwd(unrestricted)Force a working directory for all Claude sessions
--allowed-cwd-paths(any)Whitelist of cwd values clients may request
--log-levelINFODEBUG / INFO / WARNING / ERROR
--cors-origins*Allowed CORS origins

Tunnel Support

When --tunnel is omitted the server prompts interactively at startup.

ModeRequirementNotes
noneโ€”Local network only
ngrokpip install pyngrokAuth token is stored in the OS credential store on first run and loaded automatically on subsequent runs
cloudflarecloudflared binary on PATHQuick tunnel, ephemeral URL
sshSSH access to a VPSPrints the ssh -R command; no extra software needed

API Endpoints

MethodPathAuthDescription
GET/healthNoneServer status, uptime, Claude CLI version, active stream count
GET/capabilitiesBearerSupported options and server-enforced defaults
POST/queryBearerStream a claude-agent-sdk query as SSE
DELETE/query/{session_id}Bearer(501 stub โ€” reserved for future WebSocket-based cancellation)

Remote Provider (remote_claude_code)

Connects AiCore to a running aicore-proxy-server over HTTP SSE. The remote provider reconstructs the SDK message stream locally, giving the same acomplete() / complete() interface as the local provider โ€” no Claude Code CLI needed on the client side.

Prerequisites (client-side)

pip install core-for-ai   # no CLI or claude-server extras required

The proxy server must be running and reachable before instantiating the provider (a GET /health check is performed automatically at startup, controllable via skip_health_check).

Quickstart

from aicore.llm import Llm
from aicore.llm.config import LlmConfig

config = LlmConfig(
    provider="remote_claude_code",
    model="claude-sonnet-4-5-20250929",
    base_url="http://your-proxy-host:8080",   # or a tunnel URL
    api_key="your_proxy_token",               # CLAUDE_PROXY_TOKEN from server startup
)

llm = Llm.from_config(config)
response = await llm.acomplete("Summarise this codebase")
print(response)

Config File

# config/config_example_remote_claude_code.yml
llm:
  provider: "remote_claude_code"
  model: "claude-sonnet-4-5-20250929"
  base_url: "http://your-proxy-host:8080"   # or the ngrok / cloudflare tunnel URL
  api_key: "your_proxy_token"               # CLAUDE_PROXY_TOKEN printed at server startup

  # Optional โ€” forwarded to the proxy server
  permission_mode: "bypassPermissions"
  cwd: "/path/to/project"                   # must be in server's --allowed-cwd-paths
  max_turns: 10
  allowed_tools:
    - "Bash"
    - "Read"
    - "Write"

  # Skip the GET /health connectivity check at startup
  skip_health_check: false

Tool Call Streaming & Callbacks

Both claude_code and remote_claude_code emit identical tool-call events:

def on_tool_event(event: dict):
    if event["stage"] == "started":
        print(f"โ†’ Calling tool: {event['tool_name']}")
    elif event["stage"] == "concluded":
        status = "โœ—" if event["is_error"] else "โœ“"
        print(f"{status} Tool finished: {event['tool_name']}")

llm.tool_callback = on_tool_event

response = await llm.acomplete("Find all TODO comments in the codebase")

TOOL_CALL_START_TOKEN / TOOL_CALL_END_TOKEN are also emitted via stream_handler, so any existing stream consumer works without changes.

Supported Models

ModelMax TokensContext Window
claude-sonnet-4-5-2025092964 000200 000
claude-opus-4-632 000200 000
claude-haiku-4-5-2025100164 000200 000
claude-3-7-sonnet-latest64 000200 000
claude-3-5-sonnet-latest8 192200 000

Note: temperature, max_tokens, and api_key are ignored by both providers โ€” the Claude Code CLI controls model parameters internally. Cost is reported from ResultMessage.total_cost_usd rather than computed from a pricing table.


Observability

AiCore includes a comprehensive observability module that tracks:

  • Request/response metadata
  • Token usage (prompt, completion, total)
  • Latency metrics (response time, time-to-first-token)
  • Cost estimates (based on provider pricing)
  • Tool call statistics (for MCP integrations)

Dashboard Features

Observability Dashboard

Key metrics tracked:

  • Requests per minute
  • Average response time
  • Token usage trends
  • Error rates
  • Cost projections
from aicore.observability import ObservabilityDashboard

dashboard = ObservabilityDashboard(storage="observability_data.json")
dashboard.run_server(port=8050)

Built with AiCore

Reasoner4All

A Hugging Face Space showcasing reasoning-augmented models
Hugging Face Space

โฎ GitRecap

Instant summaries of Git activity
๐ŸŒ Live App
๐Ÿ“ฆ GitHub Repository

๐ŸŒ€ CodeTide & AgentTide Integration

๐Ÿ“ฆ GitHub Repository

CodeTide is a fully local, privacy-first tool for parsing and understanding Python codebases using symbolic, structural analysisโ€”no LLMs, no embeddings, just fast and deterministic code intelligence. It enables developers and AI agents to retrieve precise code context, visualize project structure, and generate atomic code changes with confidence.

AgentTide is a next-generation, precision-driven software engineering agent built on top of CodeTide. AgentTide leverages CodeTideโ€™s symbolic code understanding to plan, generate, and apply high-quality code patchesโ€”always with full context and requirements fidelity. You can interact with AgentTide via a conversational CLI or a beautiful web UI.

Live Demo: Try AgentTide on Hugging Face Spaces: https://mclovinittt-agenttidedemo.hf.space/

AiCore was used to make LLM calls within AgentTide, enabling seamless integration between local code analysis and advanced language models. This combination empowers AgentTide to deliver context-aware, production-ready code changesโ€”always under your control.

Future Plans

  • Extended Provider Support: Additional LLM and embedding providers
  • Add support for Speech: Integrate text2speech and speech to text objects with usage and observability4

Documentation

For complete documentation, including API references, advanced usage examples, and configuration guides, visit:

๐Ÿ“– Official Documentation Site