npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@snapser/mcp-server-snapser

v1.10.0

Published

Snapser MCP Server - Bridge between AI coding assistants and the Snapser platform

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

snapsersnapser

Keywords

mcpsnapseraicoding-assistant

Readme

Model context protocol (MCP)

The Model Context Protocol (MCP) is one of the new standard for connecting Large Language Models (LLMs) to platforms like Snapser. This guide covers how to connect Snapser to the following AI tools using MCP:

  • Visual Studio Code (Copilot)
  • Cursor
  • Windsurf (Codium)
  • Cline (VS Code extension)
  • Claude desktop
  • Claude code

With MCP, your AI assistants can take actions on your behalf, such as:

  1. Creating Snapends
  2. Updating Snapends
  3. Downloading custom SDKs
  4. Listing Snapends
  5. Listing all Snaps
  6. Searching Docs

We continue to add more capabilities to MCP, so check back often for updates. If you have a specific use case in mind, please reach out to us on Discord.

Setup

Step 1: Generate your Developer Key

To connect your AI tools to Snapser, you need to generate a Developer Key. This key is used to authenticate your AI tools with Snapser.

  1. Go to your Snapser Developer Dashboard.
  2. Click on the "Generate Developer Key" button.
  3. Copy the generated key and keep it safe. You will need it to connect your AI tools to Snapser.

Step 2: Create an Application / Game on Snapser

To use MCP, you need to create a application or game on Snapser. This will allow you to manage your Snapends and Snaps.

  1. Go to your Snapser Dashboard.
  2. Click on the "Create Game / Application" button.
  3. Fill in the name and click "Create".
  4. Click on the App widget to open up the App Dashboard.
  5. Copy the App Id from the App Dashboard.

Step 3: Node and NPX Installation

Before you can use MCP with your AI tools, you need to have Node.js and NPX installed on your machine. You can download Node.js from the official website. NPX is included with Node.js, so you don't need to install it separately.

IMPORTANT: For Windows, make sure node and npx are available in your PATH. If they are installed you can get the path by running npm config get prefix then you can add it to your PATH environment variable via setx PATH "%PATH%;<path-to-dir>"

Step 4: Connect your AI tools to Snapser

To connect your AI tools to Snapser, you need to configure them with your Developer Key and Application/Game Id. Follow the instructions for your specific AI tool:

Integration

Copilot - Visual Studio Code

  1. Open VS Code and create a .vscode directory in your application root if it doesn't exist.
  2. Create a .vscode/mcp.json file if it doesn't exist and open it.
  3. Add the following configuration to the mcp.json file: -- Mac OSX
    {
  "inputs": [
    {
      "type": "promptString",
      "id": "snapser-api-key",
      "description": "Snapser Developer Key",
      "password": true
    }
  ],
  "servers": {
    "snapser": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@snapser/mcp-server-snapser@latest", "--application-id=<application-id>"],
      "env": {
        "SNAPSER_API_KEY": "${input:snapser-api-key}"
      }
    }
  }
}
    • Windows
    {
  "inputs": [
    {
      "type": "promptString",
      "id": "snapser-api-key",
      "description": "Snapser Developer API Key",
      "password": true
    }
  ],
  "servers": {
    "snapser": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@snapser/mcp-server-snapser@latest", "--application-id=<application-id>"],
      "env": {
        "SNAPSER_API_KEY": "${input:snapser-api-key}"
      }
    }
  }
}
    • Windows-WSL
    {
  "inputs": [
    {
      "type": "promptString",
      "id": "snapser-api-key",
      "description": "Snapser Developer API Key",
      "password": true
    }
  ],
  "servers": {
    "snapser": {
      "type": "stdio",
      "command": "wsl",
      "args": [
        "npx",
        "-y",
        "@snapser/mcp-server-snapser@latest",
        "--application-id=<application-id>"
      ],
      "env": {
        "SNAPSER_API_KEY": "${input:snapser-api-key}"
      }
    }
  }
}
    • Linux
    {
  "inputs": [
    {
      "type": "promptString",
      "id": "snapser-api-key",
      "description": "Snapser Developer API Key",
      "password": true
    }
  ],
  "servers": {
    "snapser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@snapser/mcp-server-snapser@latest",
        "--application-id=<application-id>"
      ],
      "env": {
        "SNAPSER_API_KEY": "${input:snapser-api-key}"
      }
    }
  }
}

    IMPORTANT: Replace <application-id> with your Application/Game Id.

  4. Save the configuration file. You may see a Start Server button appear in the Editor window of the mcp.json file but do not click it just yet.
  5. Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P).
  6. Run “Developer: Reload Window” to force Copilot to reload the MCP config.
    • Alternatively, open Copilot Chat → Agents panel → “+ Add MCP Server” and select the Snapser server if prompted.
  7. Once reloaded, the Snapser MCP server should now appear in the Agents panel with a red warning icon indicating that authentication is required.
  8. Open Copilot chat and switch to "Agent" mode.
  9. If this is your first time, you will see a Red warning icon indicating that the MCP server needs setup.
  10. Click on the warning and you will be prompted to add your API Key. Enter the token that you created earlier. The warning icon should disappear. Now you can click on the Start Server button that appears in the Editor windows of the mcp.json file. Check the output window for any errors. If the server starts successfully, you should see a success message in the output log.
  11. Next, you can click tool icon in the Co-pilot chat window. In the list of tools, you should see the Snapser MCP and the commands it exposes. There should be a checkmark next to the Snapser MCP indicating that it is active.

View the Visual Studio Code MCP documentation for more information on how to use MCP with VS Code.

Cline

  1. Open the Cline extension in VS Code and tap the MCP Servers icon.
  2. Tap Configure MCP Servers to open the configuration file.
  3. Add the following configuration:
    • Mac OSX
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows
      {
    "mcpServers": {
      "snapser": {
        "command": "cmd",
        "args": [
          "/c",
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows WSL
      {
    "mcpServers": {
      "snapser": {
        "command": "wsl",
        "args": [
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Linux
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }

    IMPORTANT: Replace <application-id> with your Application/Game Id and <snapser-api-key> with your Snapser Developer Key.

  4. Save the configuration file. Cline should automatically reload the configuration.
  5. You should see a green active status after the server is successfully connected.

Cursor

  1. Open Cursor and create a .cursor directory in your application root if it doesn't exist.
  2. Create a .cursor/mcp.json file if it doesn't exist and open it.
  3. Add the following configuration to the mcp.json file:
    • Mac OSX
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows
      {
    "mcpServers": {
      "snapser": {
        "command": "cmd",
        "args": [
          "/c",
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows WSL
      {
    "mcpServers": {
      "snapser": {
        "command": "wsl",
        "args": [
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Linux
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }

    IMPORTANT: Replace <application-id> with your Application/Game Id and <snapser-api-key> with your Snapser Developer Key.

  4. Save the configuration file.
  5. Open Cursor and navigate to Settings/MCP. You should see a green active status after the server is successfully connected.

Windsurf (Codium)

  1. Open Windsurf and navigate to the Cascade assistant.

  2. Click on the hammer (MCP) icon, then Configure to open the configuration file.

  3. Add the following configuration:

    • Mac OSX
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows
      {
    "mcpServers": {
      "snapser": {
        "command": "cmd",
        "args": [
          "/c",
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows WSL
      {
    "mcpServers": {
      "snapser": {
        "command": "wsl",
        "args": [
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Linux
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }

    IMPORTANT: Replace <application-id> with your Application/Game Id and <snapser-api-key> with your Snapser Developer Key.

  4. Save the configuration file.

  5. Open Windsurf and navigate to the Cascade assistant. You should see a green active status after the server is successfully connected.

Claude desktop

  1. Open Claude desktop and navigate to Settings.
  2. Under the Developer tab, tap Edit Config to open the configuration file.
  3. Add the following configuration:
    • Mac OSX
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows
      {
    "mcpServers": {
      "snapser": {
        "command": "cmd",
        "args": [
          "/c",
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows WSL
      {
    "mcpServers": {
      "snapser": {
        "command": "wsl",
        "args": [
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Linux
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }

IMPORTANT: Replace <application-id> with your Application/Game Id and <snapser-api-key> with your Snapser Developer Key.

  1. Save the configuration file and restart Claude desktop.
  2. From the new chat screen, you should see a hammer (MCP) icon appear with the new MCP server available.

Claude Code

  1. Create a .mcp.json file in your application root if it doesn't exist.
  2. Add the following configuration:
    • Mac OSX
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows
      {
    "mcpServers": {
      "snapser": {
        "command": "cmd",
        "args": [
          "/c",
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Windows WSL
      {
    "mcpServers": {
      "snapser": {
        "command": "wsl",
        "args": [
          "npx",
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }
    • Linux
      {
    "mcpServers": {
      "snapser": {
        "command": "npx",
        "args": [
          "-y",
          "@snapser/mcp-server-snapser@latest",
          "--application-id=<application-id>"
        ],
        "env": {
          "SNAPSER_API_KEY": "<snapser-api-key>"
        }
      }
    }
  }

IMPORTANT: Replace <application-id> with your Application/Game Id and <snapser-api-key> with your Snapser Developer Key.

  1. Save the configuration file and restart Claude Code.

Enterprise / Self-hosted Snapser deployments

If you're an enterprise customer running Snapser in your own cloud, point the MCP server at your portal by setting a PORTAL_ENDPOINT environment variable. When set, this overrides the built-in Snapser-cloud endpoints — the MCP will route every API call (snapend management, SDK downloads, docs search, etc.) to your enterprise portal instead.

URL shape: the full portal base URL, including any tenant path. Examples:

https://gateway.snapser.your-company.internal/your-tenant
https://snapser.acme.com/acme

(No trailing slash needed — one will be stripped automatically.)

How to use it: add PORTAL_ENDPOINT to the env block of whichever AI-tool config you already set up above. For example, in .vscode/mcp.json:

{
  "servers": {
    "snapser": {
      "command": "npx",
      "args": ["-y", "@snapser/mcp-server-snapser@latest", "--application-id=<application-id>"],
      "env": {
        "SNAPSER_API_KEY": "${input:snapser-api-key}",
        "PORTAL_ENDPOINT": "https://gateway.snapser.your-company.internal/your-tenant"
      }
    }
  }
}

The same pattern works for Cursor, Cline, Windsurf, Claude Desktop, and Claude Code — just add the PORTAL_ENDPOINT line to the env block in their respective config files.

Your Snapser Developer Key (SNAPSER_API_KEY) and Application Id are still required — issue these from your enterprise Snapser portal rather than snapser.com.