Alice MCP Server

Alice MCP - Agile Task Management

Alice is a lightweight, local server designed to support agile task workflows within AI coding environments like those using the Model Context Protocol (MCP). It provides a backend for managing projects, tasks, epics, and messages locally on your machine, featuring project isolation to support multiple distinct software projects.

See the Documentation section for links to detailed guides.

Key Features

• Project Management: Create and manage distinct projects.
• Task & Epic Tracking: Organize work using tasks and group them into epics.
• Message Logging: Attach messages or notes to specific tasks.
• Project Isolation: All tasks, epics, and messages are scoped to a project.
• Local Operation: Runs entirely on your local machine using a simple SQLite database.
• MCP Integration: Designed to be used as a tool provider within an MCP environment.

Setup

1. Clone the repository:

   git clone <repository-url> # Replace with the actual URL
   cd alice-mcp-server
   

2. Create and activate a Python virtual environment:

   # Create the environment
   python -m venv venv
   
   # Activate it (Linux/macOS)
   source venv/bin/activate
   
   # Activate it (Windows)
   # venv\Scripts\activate
   

3. Install dependencies:

   pip install -r requirements.txt
   

Running the Server

Automatic Startup (MCP Integration)

When used with an MCP-compatible environment, Alice now starts automatically - both the FastAPI backend and the MCP server components launch together. This is handled by the scripts/start-alice-servers.sh wrapper script, which:

• Activates the Python environment
• Installs dependencies
• Starts the FastAPI server
• Starts the MCP server

Manual Startup (Development)

If you need to run the server manually (for development or testing), you can:

1. Start the FastAPI server:

   uvicorn app.main:app --reload
   

   The server will be available at http://127.0.0.1:8000

2. For debugging issues, you can run the wrapper script directly:

   /bin/zsh scripts/start-alice-servers.sh --debug
   

Getting Started

1. Start the server (see above).
2. Create a project: Send a POST request to /projects/ with a unique project name.

   { "name": "my-new-project" }
   

3. Identify your project: For interacting with tasks, epics, and messages via the Alice MCP server tools, you will use the project's name (e.g., "my-new-project") as the project_id argument. The MCP server handles the translation to the internal numeric ID required by the API.
4. API Endpoints (Direct API Usage): If interacting directly with the FastAPI backend (not through the MCP server), all subsequent operations for tasks, epics, and messages require the internal numeric project_id in the URL path (e.g., /{numeric_project_id}/tasks/). You can find this numeric ID by listing projects (GET /projects/) or getting by name (GET /projects/by-name/my-new-project).

Project Isolation API Structure

Alice's FastAPI backend uses numeric project IDs in the URL path to ensure data isolation. However, when using the Alice MCP server tools, you should provide the project's name (string) as the project_id argument. The MCP server will resolve this to the correct numeric ID for the API.

Direct API examples:

• Project Management: /projects/ (e.g., POST /projects/, GET /projects/{project_id})
• Tasks: /{numeric_project_id}/tasks/ (e.g., POST /1/tasks/, GET /1/tasks/{task_id})
• Epics: /{numeric_project_id}/epics/ (e.g., POST /1/epics/, GET /1/epics/{epic_id})
• Messages: /{numeric_project_id}/tasks/{task_id}/messages/ (e.g., POST /1/tasks/5/messages/)

Replace 1 with the actual internal numeric project_id when using the API directly.

Running Tests

Ensure you have the virtual environment activated and dependencies installed. Then run:

pytest

API Documentation

While the server is running, you can access the interactive API documentation (provided by FastAPI) in your browser:

• Swagger UI: http://127.0.0.1:8000/docs
• ReDoc: http://127.0.0.1:8000/redoc

Documentation

Detailed documentation can be found in the docs/ directory:

• Application Overview: Covers architecture, features, and technical stack.
• Technical Requirements: Detailed system, database, and API specifications.
• LLM Integration Guide: Recommendations for integrating Alice with LLM custom instructions.

Contributing

Contributions are welcome! Please follow these guidelines:

• Adhere to the coding style (PEP 8, black, isort).
• Use type hints.
• Document public functions and APIs.
• Write unit tests for new features or bug fixes.
• Ensure all tests and linters pass before submitting changes.
• For significant changes, consider opening an issue first to discuss the approach.