A Serverless MCP Server built using wasmcp, Spin and Akamai Functions
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"serverless-decision-log-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The Serverless Decision Log MCP Server illustrates how you could implement, test and run an MCP server in a truly serverless fashion. This application has been built and hosted using:
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / devops
MCP server for using the GitLab API
MCP Server for GCP environment for interacting with various Observability APIs.
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP server for Datto SaaS Protection — M365/GWS backups, restores, seats.
MCP Security Weekly
Get CVE alerts and security updates for Serverless Decision Log Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The Serverless Decision Log MCP Server illustrates how you could implement, test and run an MCP server in a truly serverless fashion. This application has been built and hosted using:
The main purpose of the MCP server is to track and provide decisions made as part of a software engineering project.
Project members can interact with the MCP server through popular clients like Visual Studio Code or other editors/IDEs.
To compile, test and deploy the Decision Log MCP Server, you must have the following tools installed on your machine:
spin CLIwasm32-wasip1 and wasm32-wasip2wasmcp CLIUse the following commands, to compile and run the Decision Log MCP Server on your local machine:
# Compiling the application
spin build
# Running the MCP server on your local machine
spin up
From the command palette chose the MCP: Add Server... command and specify the following parameters:
| Parameter | Value | Description |
|---|---|---|
| Type | HTTP | Type of our MCP Server |
| URL | http://localhost:3000 | URL of our MCP Server |
| Name | decision-log-mcp-server | Name of our MCP Server |
| Configuration Target | workspace | Configure the MCP Server for the current VS Code workspace |
The Decision Log MCP Server is deployed to Akamai Functions through the Spin CLI. You must have the aka plugin for Spin CLI installed on your machine. If you haven't installed the plugin yet, use the following command to install it:
# Install the aka plugin for Spin CLI
spin plugins install aka
With the aka plugin for Spin CLI installed on your machine, you must authorize it for interacting with Akamai Functions on your behalf:
# Authorize Spin CLI for interacting with Akamai Functions on your behalf
spin aka login
Once you've authorized the Spin CLI to interact with your Akamai Functions account, you can deploy the application using the spin aka deploy command:
# Deploy the MCP Server to Akamai Functions
spin aka deploy
Follow the instructions and confirm the deployment. Deploying an application to Akamai Functions takes roughly 45 seconds. During that time, your application will be deployed to all service regions across the globe. A generic subdomain will be registered and assigned to your application as well.
Once deployment has finished, you can update the MCP Server configuration in your client (e.g., Visual Studio Code) and point to the URL generated by Akamai Functions as part of the deployment.