4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
LocalAI MCP Server

Bring Self Hosted
to CrewAI

Learn how to connect LocalAI to CrewAI and start using 19 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Anthropic MessagesApply ModelChat CompletionsCreate EmbeddingsDetect ObjectsFace AnalyzeFace IdentifyFace RegisterFace VerifyGenerate ImageGet Auth StatusGet Auth UsageGet System InfoGet VersionList ModelsOpen ResponsesRerank DocumentsText To SpeechTranscribe Audio

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
LocalAI

What is the LocalAI MCP Server?

Connect your LocalAI instance to any AI agent and leverage powerful multimodal capabilities directly from your own infrastructure.

What you can do

  • Text Generation — Use chat_completions or anthropic_messages to generate text using local models with full OpenAI or Anthropic compatibility.
  • Image Synthesis — Create visual content from text prompts using the generate_image tool, supporting custom sizes and negative prompts.
  • Audio Processing — Convert speech to text with transcribe_audio or generate natural-sounding speech from text using text_to_speech.
  • Advanced Search & RAG — Generate vector embeddings with create_embeddings and improve search relevance using the rerank_documents tool.
  • Computer Vision — Analyze images and identify elements using the detect_objects tool.
  • System Management — Monitor your instance with list_models, get_system, and getVersion to ensure optimal performance.

How it works

  1. Subscribe to this server
  2. Provide your LocalAI Base URL (e.g., http://localhost:8080) and optional API Key
  3. Start interacting with your local models through Claude, Cursor, or any MCP client

Who is this for?

  • Privacy-Conscious Developers — Run powerful AI workflows without sending sensitive data to third-party cloud providers.
  • AI Researchers — Easily test and swap different local models for chat, vision, and audio tasks.
  • DevOps Engineers — Integrate local AI capabilities into internal tools and automated pipelines.

Built-in capabilities (19)

anthropic_messages

Generate messages (Anthropic compatible)

apply_model

Install a model from the gallery

chat_completions

Generate chat completions (OpenAI compatible)

create_embeddings

Create text embeddings

detect_objects

Detect objects in an image

face_analyze

Analyze face demographics

face_identify

Identify faces (1:N)

face_register

Enroll a face into the store

face_verify

Verify faces (1:1)

generate_image

Supports negative prompts using | separator. Generate images from text prompts

get_auth_status

Check authentication state and providers

get_auth_usage

View personal token usage

get_system_info

View system and backend info

get_version

Get LocalAI version

list_models

List available models

open_responses

Generate open responses

rerank_documents

Rerank documents based on a query

text_to_speech

Convert text to audio (TTS)

transcribe_audio

Pass the file data or path as required by your LocalAI setup. Transcribe audio to text

Why CrewAI?

When paired with CrewAI, LocalAI becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call LocalAI tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

LocalAI in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

LocalAI and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect LocalAI to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for LocalAI in CrewAI

The LocalAI MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 19 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

LocalAI
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures LocalAI for CrewAI

Every tool call from CrewAI to the LocalAI MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I see which AI models are currently installed on my LocalAI server?

You can use the list_models tool. It will return a complete list of all available models on your instance, including their IDs and capabilities.

02

Does this server support generating images locally?

Yes! By using the generate_image tool, you can provide a prompt and optional size to generate images directly on your hardware using supported models like Stable Diffusion.

03

Can I use this to transcribe audio files into text?

Absolutely. The transcribe_audio tool allows you to send audio data or file paths to your LocalAI instance for high-quality transcription using models like Whisper.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →