Get Started

Run the MCP Server Reliably

Configure the local MCP server, start it when your tools are ready, and use the status and log panels to recover quickly when a client cannot connect.

Updated: May 13, 2026

What you need

  • Server: open the Server section from the app sidebar.
  • Port choice: keep the default unless another service already uses it.
  • Client plan: decide whether clients connect through localhost or all interfaces.

Quick links

Quick Start Settings HTTPS Common Errors Next Steps

Quick start in 5 steps

  1. Open Server in the sidebar.
  2. Review Server Name, Server Title, Server Version, and Listening Port.
  3. Choose whether Listen all interfaces should stay off for localhost-only use or be enabled for network clients.
  4. Click Save, then click Start.
  5. Copy the displayed server URL and confirm the Server Log shows the server is running.

Configure runtime behavior before starting

Server fields are disabled while the server is running. Stop the server before changing identity, port, interface, HTTPS, certificate, or instruction settings.

  • Auth Token: copy it into clients that require authenticated MCP access. Clear it only when the server is stopped.
  • Instruction: describe server-level guidance that clients should receive with the MCP configuration.
  • Server Log: keep it visible when testing a new client or troubleshooting a failed start.
The toolbar shortcuts are useful while testing: Start uses Command-R, Stop uses Command-X, and Save uses Command-S.

Use HTTPS only when certificates are ready

The HTTPS Certificate panel shows certificate status, subject, SANs, CA count, and SHA-256 fingerprint. Import a CA certificate and TLS identity before enabling HTTPS for clients that verify certificates.

  • Import CA Cert.: adds the certificate authority chain.
  • Import TLS Cert.: adds the server identity used by the HTTPS listener.
  • Copy PEM: copies certificate material for client configuration or inspection.
Do not enable Listen all interfaces unless you intend to expose the server beyond localhost and have reviewed token and certificate settings.

Common errors and quick fixes

  • Port is already in use: stop the other service or choose a different Listening Port, save, then start again.
  • Client cannot connect: copy the URL from the status row and confirm the client uses the same HTTP or HTTPS scheme.
  • Network client fails from another device: enable Listen all interfaces only if network access is intended.
  • HTTPS fails: check the certificate status and fingerprint, then re-import the CA or TLS identity while the server is stopped.

Next steps