Template repository for creating a WebAssembly component Model Context Protocol (MCP) Server, with wasmCloud.
- Download
wash
Build the component:
npm install
npm run devTo debug your component, we recommend using the official MCP model inspector, to run that you can run:
npm run inspectorUsing the model inspector you can connect to the local MCP server via HTTP, manipulate resources, run tools, and more.
wash new <...>Once your MCP server is ready for primetime, ensure your Comonic cluster is running.
Don't have a Comsonic cluster set up?
First, sign up for a FREE Cosmonic license.
Once you have a license key, you can set up a Cosmonic cluster on any Kubernetes cluster that supports Helm:
helm install cosmonic-control oci://ghcr.io/cosmonic/cosmonic-control \
--version 0.2.0 \
--namespace cosmonic-system \
--create-namespace \
--set cosmonicLicenseKey="<insert license here>"
helm install hostgroup oci://ghcr.io/cosmonic/cosmonic-control-hostgroup --version 0.2.0 --namespace cosmonic-system --set http.enabled=trueWith the operator up and running we can start a HostGroup, which is a set of wasmCloud
instances that are configured to work together.
# Note substitue your own pushed image
helm install weather-gov-mcp oci://ghcr.io/cosmonic-labs/charts/http-sample \
-n weather-gov --create-namespace \
--set component.image=ghcr.io/cosmonic-labs/components/weather-gov-mcp:0.1.0 \
--set component.name=weather-gov-mcp If running with a k8s cluster, you can port forward:
kubectl -n cosmonic-system port-forward svc/hostgroup-default 9091:9091Once you have a local port forward configured to your Cosmonic Control cluster, use the official MCP model inspector to connect.
You can start the MCP inspector via the following command:
npm run inspector