Serverless Decision Log MCP Server
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:
Усильте агента
Установка от издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
В реестре пока нет пакетного релиза. Следуйте README репозитория.
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускОт издателя
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:
A Serverless MCP Server built using wasmcp, Spin and Akamai Functions
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:
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.
A Serverless MCP Server built using wasmcp, Spin and Akamai Functions
Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
Serverless Decision Log работает локально через stdio.
Последняя проверка: 2026-11-05. A Serverless MCP Server built using wasmcp, Spin and Akamai Functions