Skip to content

MCP server tutorial: deploy your first MCP server

Guides · 6 min read

A step-by-step MCP server tutorial: install the gxmesh CLI, build an MCP server with one tool in Go, TypeScript or Python, deploy it and connect a client.

Three stacked plates of a project rise along a beam of light through a green test ring to a glowing endpoint.

In this post

  • Install the gxmesh CLI on macOS, Linux or Windows
  • Start a project and add a tool in Go, TypeScript or Python
  • Push it and connect an MCP client
You needA terminalA Glxymesh accountAbout 10 minutes

This tutorial builds an MCP server with one tool and deploys it in about ten minutes. Glxymesh hosts the server, so you don't run one yourself. A tool is a tool.yml that describes it, plus one run function in Go, TypeScript or Python if it needs code. You push the project; the platform builds it, runs its tests and serves it from one authenticated endpoint.

Install the CLI#

The gxmesh CLI starts projects, runs them on your machine and deploys them. Pick your system:

$ curl -fsSL https://platform.glxymesh.com/install.sh | bash

Sign in and create a project#

Sign in, choose your organization, then create the project that will hold your tools. A project is one MCP server, with its own tools and secrets.

terminal
$ gxmesh login
$ gxmesh org use
$ gxmesh project create helpdesk

Start the project and add a tool#

Make a folder for the project, pick its language, and add a tool. You get a tool.yml and a code file to edit in any editor.

terminal
$ mkdir acme-helpdesk && cd acme-helpdesk
$ gxmesh init --lang node --project helpdesk
$ gxmesh new list-open-issues

Deploy#

gxmesh dev serves the project on your machine as an MCP server. When it works, push it: the platform builds it, runs the tests in each tool.yml, and puts it live only if they pass.

terminal
$ gxmesh push
Diagram: gxmesh push builds one Lambda, runs the tests in each tool.yml, and goes live on acme.mcp.glxymesh.com/helpdesk only if all pass; if one fails, live stays as it was.
A push goes live only when every test passes. If one fails, the version already live keeps serving.

Connect a client#

gxmesh connect prints your project's address and the command to add it to Claude Code, Cursor and other clients. The console's Connect page shows the same.

The console's Connect page: the project address, its transport and sign-in, the command for Claude Code, and the steps that happen when a client connects.
The Connect page, here for a demo project. Each client signs in for itself, so there is no API key to hand out.
CommandWhat it does
gxmesh initStarts a project in this folder
gxmesh newAdds a tool
gxmesh devServes the project on your machine
gxmesh pushBuilds, tests and deploys it
gxmesh connectShows how to connect a client

Glxymesh team

The people building the platform. Questions about this post go to support@glxymesh.com.

Next postKeeping API keys out of your tool code →