Aica MCP Server

Connect Aica to Claude, Cursor or any other MCP client and it stops being a tab you switch to. aica(AI Code Analyzer) reviews your code using AI. Supports CLI and GitHub Actions. The aica mcp server is what makes that connection.

What the server does

So, I decided to create a new tool with the following characteristics:

• AI Coding Agent
• AI Code Review
• MCP(Model Context Protocol) supported. stdio and SSE transports are supported
• Automatic knowledge retrieving for code review
• Symbol based code search for retrieving knowledge
• Vector based document search for retrieving knowledge

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• aica — -version: Show version information
• Language — You can specify the language for AI output. The language can be specified either through AICA_LANGUAGE or in the language section of aica.toml. By
• Review — The Review tool exposed by this server
• Agent — The Agent tool exposed by this server
• Reindex — The Reindex tool exposed by this server
• Summary — The Summary tool exposed by this server
• Setup — See wiki page for details
• Commands — You can interact with AI features by leaving comments with the following commands

Credentials and setup notes

Configuration is passed through the environment: GITHUB_TOKEN, AICA_LLM_PROVIDER, ANTHROPIC_API_KEY, ANTHROPIC_MODEL, OPENAI_API_KEY, OPENAI_MODEL, GOOGLE_API_KEY, GOOGLE_MODEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aica's toolset — aica, Language, Review and 5 more — is a fair guide to whether it matches your workflow. It is maintained by dotneet; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.