Local Servers

Introduction

Many MCP servers today are provided either as an uvx and npx command. These one-liners download and install a Python or NodeJS application and start it. To use such MCP Servers in Gatana, you should create a Local server in your Gateway.

The server application may provide one of following transports:

• Standard I/O: the common transport for local servers
• HTTP Streaming or SSE: some local servers use HTTP as a transport. This is particularly useful when using OAuth credentials

The following configuration options are available:

• Command (for example uvx workspace-mcp)
• Environment Variables
• Headers (in case of HTTP transport)
• Files (the provided files will be available in the same folder as the app is running)

Credentials accessed using these expressions:

• API Keys: {{ credentials.keys.MY_API_KEY }}
• OAuth Access Token: {{ credentials.accesstoken }}

See the Gateway documentation for information about credentials.

Deployment and Output Logs

When you create or update a server, Gatana will automatically deploy the server. You can click on Deployment logs in the Gatana App to see the status of the current revision.

The output logs can be viewed in the server details view, under the Server Logs section. In the dropdown, select a revision, and the browser will begin stream the logs to your browser.

Environment and Isolation

The operating system is Debian Bookworm. Each local server is being executed in an containerized environment using containerd and gVisor, which provides a strong layer of security and isolation.