serverless-decision-log

This MCP server implements a serverless decision log that tracks and serves decisions made during a software engineering project. It is designed to run with the Spin framework and Akamai Functions, enabling you to deploy and run the MCP server in a serverless environment or locally for development. You can interact with the server using standard MCP clients or editors like Visual Studio Code via the MCP extension, and you can deploy the server to Akamai Functions for global availability. The local workflow involves building the WASM module with Spin and then running the server locally with Spin, after which you can point your MCP clients at http://localhost:3000 (or the deployed endpoint) to query decisions or submit new ones.

Prerequisites:

• Install Spin CLI (spin)
• Install Rust and the required targets wasm32-wasi or wasm32-wasip1/wasm32-wasip2 as appropriate for your environment
• Install wasmCP CLI (wasmcp)

Step-by-step:

1. Install prerequisites

   • Follow Spin installation instructions: https://spin.ninja/docs/getting-started/
   • Ensure Rust is installed and add targets: rustup target add wasm32-wasip1 rustup target add wasm32-wasip2
   • Install wasmcp CLI (per its documentation)

2. Set up the MCP server locally

   • Clone or download the repository containing the Decision Log MCP Server

   • Navigate to the project directory

   • Build the WASM artifact configured for Spin:

     spin build

3. Run the MCP server locally for development

   • Start the server with Spin:

     spin up

4. Prepare for deployment (optional)

   • Install the aka plugin for Spin CLI if you plan to deploy to Akamai Functions:

     spin plugins install aka

   • Authenticate with Akamai Functions via Spin:

     spin aka login

   • Deploy to Akamai Functions:

     spin aka deploy

Notes:

• Ensure the appropriate WASI targets are installed for your runtime environment.
• The local port for the MCP server typically defaults to http://localhost:3000, which you can configure in your MCP client.

Tips and common issues:

• If spin build or spin up fails, verify that the Rust targets (wasm32-wasip1/wasm32-wasip2) are installed and that your environment has the necessary toolchain versions.
• When deploying to Akamai Functions, ensure you have the aka plugin installed and that you are authenticated before running spin aka deploy.
• After deployment, update your MCP client configuration to point at the generated Akamai Functions URL.
• The MCP server is designed for a serverless workflow; you can still develop and test locally using spin up before deploying.
• If you encounter port conflicts, adjust your local configuration or use a different port mapping in your local Spin setup.