code-assistant

Code Assistant is an AI coding assistant written in Rust that can operate as an MCP server in addition to its GUI and CLI modes. In MCP server mode, it exposes its capabilities so MCP clients (like Claude Desktop) can start a persistent session, request code analysis and modification, and stream tool invocations in real time. The server supports multiple tool invocation modes (native function calling, XML-style tags, and triple-caret blocks) to stay compatible with a variety of AI providers. It also integrates with ACP-compatible editors and can manage session-based project state, including per-session memory and draft messages with attachment support. When running as an MCP server, you can connect an MCP client to the server endpoint and issue commands that align with the Agent Client Protocol (ACP) style of request/response, including pending messages, streaming updates, and tool executions with appropriate permissions. It also auto-loads repository guidance from AGENTS.md (or CLAUDE.md fallback) to align the assistant’s behavior with the project’s norms. To use it, start the server in MCP mode and point your MCP client at the server, then follow the client’s workflow to start a session, load a project, and issue tasks such as analyzing a code path or suggesting refactors. The server is designed to work well with editors and environments that support ACP and JSON-RPC over stdin/stdout when used in ACP mode, providing real-time feedback and structured tool results.

Prerequisites:

• Rust toolchain (stable) installed (Rustup recommended)
• Build tools for your platform (e.g., build-essential on Linux, Xcode command line tools on macOS)

Install and build:

1. Install Rust toolchain

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

2. Clone the repository and build

git clone https://github.com/stippi/code-assistant
cd code-assistant
cargo build --release

3. Confirm the binary exists

ls -l target/release/code-assistant

4. Create and edit configuration files as described in the README (providers.json, models.json, projects.json) under ~/.config/code-assistant and export your API keys as environment variables if required (e.g., ANTHROPIC_API_KEY, OPENAI_API_KEY).

Running in MCP server mode:

./target/release/code-assistant server

Optional: If you plan to integrate with Claude Desktop or other MCP clients, ensure the server is reachable by the client and that you configure any required environment variables or paths as described in the Claude Desktop integration notes.

Tips and caveats:

• The MCP server mode relies on the Rust binary built in release mode; ensure you’re running the latest built artifact.
• When configuring projects, remember that each chat session is permanently tied to its initial project and folder; change affects should be planned accordingly.
• Tool invocation modes (native/xml/caret) are fixed per session at creation time; verify compatibility with your MCP client’s capabilities.
• If you enable format-on-save and use a temporary project, the assistant can still operate within the temporary project context for that session.
• For ACP users, the server communicates via JSON-RPC over stdin/stdout; ensure your client is prepared to handle streaming and pending messages.
• Ensure environment variables for API keys are kept secure and not committed to version control.