Ava MCP Adapter
Proxies MCP tool requests to a FastAPI-based Ava_Agent service, enabling AI agents to interact with CommandDeck specialist brains through chat, project management, task submission, memory operations, skill invocation, and Git operations.
Provides Git integration tools for checking repository status, viewing commit logs, and creating commits within project contexts through the Ava_Agent system.
Supports deployment on Render cloud platform with environment variable configuration for API keys and service URLs, enabling cloud-hosted MCP server operation.
Uses YAML configuration for Render deployment setup, allowing declarative infrastructure definition for the MCP server deployment.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ava MCP Adapterchat with me about optimizing our deployment pipeline"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ava MCP Adapter
Thin REST bridge that implements JarvisEPC's MCP tool-server contract
(GET /tools, POST /execute, GET /health) and proxies each tool to
the deployed Ava_Agent at https://ava-agent-qzmu.onrender.com, which
in turn routes to CommandDeck specialist brains.
Why
JarvisEPC's api/routes/mcp.ts expects a REST tool server shape. The
existing Ava_Agent speaks FastAPI domain-specific endpoints (/chat,
/projects/.../tasks, /broadcast, /v1/skills/invoke, ...) — this
adapter is the glue that maps the REST contract onto those endpoints.
Related MCP server: Bridge MCP Server
Tools exposed
name | category | upstream |
| AI |
|
| System |
|
| System |
|
| AI |
|
| AI |
|
| AI |
|
| AI |
|
| AI |
|
| System |
|
| System |
|
| System |
|
Deploy
Already wired to Render via render.yaml. Set AVA_AGENT_API_KEY
(copied from the Ava_Agent service env) in the Render dashboard.
Wire AVA_MCP_URL=https://ava-mcp-adapter.onrender.com into the
JarvisEPC service env; the MCP tab will switch from "Ava offline" to
showing the full merged tool catalog.
This server cannot be deployed
Maintenance
Related MCP Connectors
Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs.
Shared memory for connected AI tools. Projects, rules and skills over MCP. OAuth or API key.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Related MCP Servers
- AlicenseAqualityFmaintenanceA bridge server that enables MCP-compatible AI assistants like Claude to seamlessly discover, communicate with, and manage A2A protocol agents.7148Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceBridge is a hosted MCP server that connects AI models to business tools like ClickUp and a repository of pre-built workflow skills. It enables direct interaction with project management tools and automated instruction sets through natural language.-
- AlicenseNot gradedqualityDmaintenanceA bridge that enables any LLM to access and interact with documented REST APIs through the Model Context Protocol (MCP).5 npm6MIT
- AlicenseNot gradedqualityCmaintenanceBridges LLM clients with existing RESTful microservices by converting MCP tool calls into REST requests, enabling any REST API to be used as an MCP tool without modifying the microservices.486,710 npm1MIT