⌁ CURSOR + LOCALHOST MCP

Use Cursor with an MCP server on localhost

Cursor speaks MCP over HTTPS. Tapinto gives your localhost a public HTTPS URL in one command — so Cursor can call your tools while you build them. First 60 minutes per week are free.

Start free

first 60 min / week free · from $0.001 / tunnel-minute · $0.002 / mcp-toolkit-minute · USD billing

The fast path: let Cursor run it for itself

Cursor speaks MCP both as a client and as a host. Wire the Tapinto CLI as an MCP server in Cursor's settings and Cursor can call create_tunnel itself — no terminal, no copy-paste of a URL. The first call auto-registers an anonymous 60 min/week trial bound to your machine, so you can demo this without signing up.

ADD TO CURSOR MCP CONFIG

{
  "mcpServers": {
    "tapinto": {
      "command": "tapinto",
      "args": ["mcp"]
    }
  }
}

~/.cursor/mcp.json (or: Settings → Tools & Integrations → MCP → Add server)

Restart your AI host after editing the config. First create_tunnel call auto-registers an anonymous 60 min/week trial — no signup, no card.

The classic path: three commands, paste a URL

Prefer to drive the tunnel from a terminal? Open it yourself and add the public URL to Cursor's MCP server list.

# 1. Install
$ curl -fsSL https://raw.githubusercontent.com/Cre8-IT-Code/tapinto-cli/main/install.sh | bash

# 2. Tunnel your local MCP server
$ tapinto https://localhost:8080 --inspect
✓ Tunnel active: https://amber-fern-3a8.tapinto.it

# 3. Paste that URL into Cursor → Settings → MCP

Why a tunnel?

Cursor talks to MCP servers over HTTPS. A server on localhost:8080 isn't reachable from Cursor's cloud-side components. Tapinto inverts the direction: your CLI opens an outbound WebSocket to the Tapinto edge, the edge holds it open, and inbound requests to https://<slug>.tapinto.it are shoveled down that socket to your local process. No port forwarding, no firewall changes.