Hitchcode MCP Server

Provides a template for creating custom tools for the Cursor IDE using the Model Context Protocol (MCP).

Local serverstdioPython 2

What is the Hitchcode MCP server?

Hitchcode MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Provides a template for creating custom tools for the Cursor IDE using the Model Context Protocol (MCP).

What you get

A simple template for creating custom tools for Cursor IDE using Model Context Protocol (MCP). Create your own repository from this template, modify the tools, and connect them to your Cursor IDE.

What the assistant can call

Once Hitchcode is connected, these are the calls the assistant has available:

  • Type — Select "sse"
  • URL — Enter http://localhost:8000/sse
  • Name — Choose any name (e.g., "my-mcp-server-1")
  • Command — Paste the absolute path to cursor-run-mcp-server.sh that you copied earlier. For example: /Users/kirillmarkin/weaviate-mcp-server/cursor-run-mcp-serve
  • MCP_USER_AGENT — Custom User-Agent for website fetching

Setting it up

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: MCP_SERVER_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hitchcode's toolset — Type, URL, Name and 2 more — is a fair guide to whether it matches your workflow. It is maintained by jankowtf; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the hitchcode mcp server does with a few real requests.

Available tools

ToolWhat it does
TypeSelect "sse"
URLEnter http://localhost:8000/sse
NameChoose any name (e.g., "my-mcp-server-1")
CommandPaste the absolute path to cursor-run-mcp-server.sh that you copied earlier. For example: /Users/kirillmarkin/weaviate-mcp-server/cursor-run-mcp-server.sh
MCP_USER_AGENTCustom User-Agent for website fetching

How to install the Hitchcode MCP server

{
  "mcpServers": {
    "hitchcode": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "MCP_SERVER_HOST": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_SERVER_HOSTEndpoint or connection string the server talks to.Optional

Example prompts to try

  • Use Hitchcode to Type.
  • Use Hitchcode to URL.
  • Use Hitchcode to Name.

Frequently asked questions

MCP enables communication between Cursor IDE and external tools, allowing for enhanced functionality and integrations. Hitchcode provides a structured way to implement this protocol.