Skip to content

Cursor snapforge snapforge_signup

How to: Cursor snapforge snapforge_signup

client:Cursor transport:streamable-http tool:snapforge_signup

Add snapforge to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "snapforge": {
      "url": "https://snapforge.org/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something snapforge_signup does. Cursor lists the server's tools on connect and calls snapforge_signup itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that snapforge's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

snapforge will not start until these are set, so snapforge_signup never becomes available.

  • SNAPFORGE_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.