Spikes

Name: Spikes
Author: bierlingm

by bierlingmversion 0.4.1i★ –iRuns on your computer

Registry nameio.github.bierlingm/spikes

Install

Overview

Description from the maker (original English)

UI feedback for AI-assisted building. Click elements, rate them, agents triage via MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: SPIKES_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SPIKES_TOKEN, SPIKES_API_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "spikes": {
      "command": "npx",
      "args": [
        "-y",
        "spikes-mcp"
      ],
      "env": {
        "SPIKES_TOKEN": "your-value",
        "SPIKES_API_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add spikes --env SPIKES_TOKEN=your-value --env SPIKES_API_URL=your-value -- npx -y spikes-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "spikes": {
      "command": "npx",
      "args": [
        "-y",
        "spikes-mcp"
      ],
      "env": {
        "SPIKES_TOKEN": "your-value",
        "SPIKES_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "spikes": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "spikes-mcp"
      ],
      "env": {
        "SPIKES_TOKEN": "your-value",
        "SPIKES_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SPIKES_TOKEN secret env
Bearer token for the hosted Spikes API. Required only when using --remote mode against spikes.sh. Local mode reads .spikes/feedback.jsonl and needs no token.
SPIKES_API_URL env
Override the Spikes API base URL. Defaults to https://spikes.sh/api. Useful for self-hosted Spikes workers.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account bierlingm, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32599 servers in this category
Published to the registry more recently than 8% of the other 32599 servers in this category
Basic checks equal to or better than 100% of the other 32599 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Spikes safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SPIKES_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Zendesk

by pipeworx-io

Zendesk MCP Pack — tickets, users, organizations via OAuth.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

/ Spikes

The feedback loop for AI-assisted building

AI can build a prototype in an hour.

Turning feedback into action is still the slow part.

Quick Start · CLI Reference · Widget Docs · Hosted Dashboard · Self-Hosting

What Is This?

Spikes is a feedback tool for AI-assisted development. It lets reviewers leave targeted feedback directly on web pages — no screenshots, no "that button over there", no lost context.

Click any element. Rate it. Comment. Spikes captures the exact CSS selector, bounding box, and page context. Your AI agent gets structured JSON it can act on immediately.

No accounts required. No build step. Works on `file://`, localhost, anywhere.

Quick Start

1. Install the CLI

curl -fsSL https://spikes.sh/install.sh | sh

Or: cargo install spikes

2. Initialize your project

spikes init                     # Defaults to hosted spikes.sh

spikes init --self-host # Opt out — scaffold a self-hosted config instead

spikes init creates .spikes/config.toml with a [remote] section pointing at https://spikes.sh by default. Pass --self-host (or answer s at the prompt) to skip the hosted defaults.

3. Add the widget to your HTML

spikes inject ./mockups/        # Injects widget script tag (uses configured endpoint)

spikes serve # http://localhost:3847

4. Collect and use feedback

spikes list                     # See all feedback

spikes list --json # Feed to your agent spikes list --rating no # Find problems spikes hotspots # Elements with most feedback spikes resolve # Mark items done

CLI Commands

Command	Description
`spikes init`	Create `.spikes/` directory with config (hosted by default; `--self-host` to opt out)
`spikes list`	List feedback (`--json`, `--page`, `--reviewer`, `--rating`, `--unresolved`)
`spikes show`	Show single spike details
`spikes export`	Export to JSON/CSV/JSONL/Cursor/Claude context
`spikes hotspots`	Elements with most feedback
`spikes reviewers`	List all reviewers
`spikes inject`	Add/remove widget from HTML files (`--endpoint` overrides the configured endpoint)
`spikes serve`	Local dev server (`--port`, `--marked`, `--cors-allow-origin`)
`spikes mcp serve`	Start MCP server for AI agent integration
`spikes pull/push/sync`	Sync with remote endpoint
`spikes share`	Upload to spikes.sh for instant sharing
`spikes login/logout/whoami`	Authentication management
`spikes upgrade/billing`	Pro tier subscription via Stripe
`spikes deploy cloudflare`	Scaffold self-hosted Worker + D1

All commands support --json for scripting. See full CLI reference.

Viewing spikes for a hosted project:

The hosted dashboard at [https://spikes.sh/dashboard](https://spikes.sh/dashboard) lists every project you own and lets you drill into individual spikes (filter by page, rating, resolved, toggle resolved inline). Sign in directly in your browser: click Sign in, open the verification page, and confirm via the magic link sent to your email — no CLI required.

You can also hit the JSON API directly with your bearer token ($SPIKES_TOKEN from spikes login):

# GET /me/projects

List all projects you own (with spike_count + last_activity)

curl -H "Authorization: Bearer $SPIKES_TOKEN" \ https://spikes.sh/me/projects

GET /me/projects/:key/spikes

List spikes for one of your projects (paginated, filterable: page, per_page,

filter_page, filter_rating, filter_resolved)

curl -H "Authorization: Bearer $SPIKES_TOKEN" \ "https://spikes.sh/me/projects/my-project/spikes?page=1&per_page=50"

PATCH /me/projects/:key/spikes/:id

Toggle the `resolved` flag on one spike

curl -X PATCH -H "Authorization: Bearer $SPIKES_TOKEN" \ -H "Content-Type: application/json" \ -d '{"resolved": true}' \ https://spikes.sh/me/projects/my-project/spikes/

POST /projects

Create a new project (user bearer only)

curl -X POST -H "Authorization: Bearer $SPIKES_TOKEN" \ -H "Content-Type: application/json" \ -d '{"key": "my-project", "allowed_origins": ["https://example.com"]}' \ https://spikes.sh/projects

Single-line variant (copy-paste friendly)

curl -H "Authorization: Bearer $SPIKES_TOKEN" https://spikes.sh/me/projects

All /me/* endpoints are user-scoped: you only ever see projects and spikes you own. Cross-tenant requests return 404 PROJECT_NOT_FOUND (enumeration-proof).

Security note: API keys (sk_spikes_*) and the admin SPIKES_TOKEN are not accepted on /me/* endpoints or POST /projects — those require a user bearer token from spikes login. The POST /spikes collect endpoint enforces a per-project origin allowlist and per-project rate limits; rejected widget requests surface as a small red #spikes-error-dot indicator on the widget button (404 / 403 / 429).

AI Agent Integration

Spikes speaks agent natively. Your AI coding assistant can read, write, and manage feedback without ever leaving its workflow.

npx spikes-mcp            # Zero-install MCP server — just works

or: spikes mcp serve # If you have the CLI installed

MCP Server — 16 Tools

spikes mcp serve starts a Model Context Protocol server that exposes 16 tools:

Tool	Purpose
`get_spikes`	List feedback with filters (page, rating, unresolved, url_prefix, since)
`get_element_feedback`	Get feedback for a specific CSS selector
`get_hotspots`	Find elements with the most feedback
`submit_spike`	Create feedback programmatically
`resolve_spike`	Mark feedback as addressed
`delete_spike`	Remove a spike
`create_share`	Upload files, get a shareable URL
`list_shares`	See your active shares
`get_usage`	Check usage stats, limits, and spend
`reply_to_spike`	Answer a reviewer on the page, optionally with a status and version (hosted)
`set_spike_status`	Mark a spike open, addressed, or won't do (hosted)
`list_versions` / `add_version`	Declare review versions and see counts per version (hosted)
`list_questions` / `ask_question` / `get_question_answers`	Ask reviewers questions and read answers (hosted)

Supports stdio and HTTP transports, local and remote data modes:

spikes mcp serve                              # stdio, local JSONL

spikes mcp serve --remote # stdio, hosted API spikes mcp serve --transport http --port 3848 # HTTP for sandboxed agents

API Keys

Agents get their own identity. No email, no magic link, no human step:

spikes auth create-key --name "my-agent"   # → sk_spikes_...

spikes auth list-keys # See all keys spikes auth revoke-key # Revoke

Keys support read/write/full scopes and optional budget caps.

Agent-Tier Billing

Consumption-based pricing for agent-scale usage. Pay per spike, not per seat:

spikes usage    # See current spend and limits

Budget enforcement returns 429 BUDGET_EXCEEDED when caps are hit — agents can check before they burn.

Context Exports

Export structured markdown optimized for agent consumption:

spikes export --format cursor-context > cursor-feedback.md

spikes export --format claude-context > claude-feedback.md

Discovery

[llms.txt](https://spikes.sh/llms.txt) — All 9 MCP tools, parameters, agent quickstart
[agents.md](https://spikes.sh/agents.md) — Machine-readable landing page for agents
[Smithery](https://smithery.ai) — Listed in the MCP server registry
spikes mcp install — Generates config for Claude Desktop / Cursor

Full details: llms.txt · agents.md

GitHub Action

Gate CI on feedback quality. The spikes-action fails builds when unresolved negative feedback exceeds your threshold.

name: CI

on: [push, pull_request]

jobs: feedback-gate: runs-on: ubuntu-latest steps:

uses: actions/checkout@v4
uses: bierlingm/spikes/action@v0.3.1 with: threshold: 0 # Fail if any blocking spikes ignore-paths: "" # Optional: pages to ignore require-resolution: false

See action/README.md for full documentation.

Widget Attributes

Simple setup — just add your project key and you're ready to collect feedback:

<script src="https://spikes.sh/spikes.js" data-project="my-app"></script>

When you set data-project, feedback syncs automatically to https://spikes.sh/spikes. No need to configure an endpoint unless you're self-hosting.

Full configuration — all available attributes:

<script src="https://spikes.sh/spikes.js"

data-project="my-app" data-position="bottom-right" data-color="#e74c3c" data-theme="dark" data-reviewer="Pat" data-collect-email="true" data-admin="true">

Self-hosting — point to your own backend:

<script src="/spikes.js"

data-project="my-app" data-endpoint="https://my-worker.workers.dev/spikes">

Attribute	Description	Default
`data-project`	Group feedback by project key	`location.hostname`
`data-position`	Button corner: `bottom-right`, `bottom-left`, `top-right`, `top-left`	`bottom-right`
`data-color`	Accent color (any CSS color)	`#e74c3c`
`data-theme`	Modal theme: `dark` or `light`	`dark`
`data-reviewer`	Pre-set reviewer name	(prompts user)
`data-endpoint`	Backend URL for multi-reviewer sync. Optional — defaults to `https://spikes.sh/spikes` when `data-project` is set.	`https://spikes.sh/spikes` (with `data-project`), `/spikes` (local dev)
`data-collect-email`	Show email field in prompt	`false`
`data-admin`	Enable review mode features	`false`
`data-offset-x/y`	Button offset from edge	—

See Widget Attributes Reference for complete documentation.

Architecture

Spikes has three components that work together or standalone:

┌─────────────┐     ┌─────────────┐     ┌─────────────┐

│ CLI │────▶│ Widget │◄────│ Worker │ │ (Rust) │ │ (Vanilla │ │ (Cloudflare │ │ │ │ JS) │ │ + D1) │ └─────────────┘ └─────────────┘ └─────────────┘ │ │ │ spikes.sh (hosted) │ └────────────────────────────────────────────┘

CLI — Rust binary for local development, spike management, and deployment. Stores spikes in ~/.local/share/spikes/.

Widget — 14KB gzipped vanilla JS. Captures element selectors, bounding boxes, ratings, and comments. Works offline via localStorage.

Worker — Optional Cloudflare Worker + D1 backend for multi-reviewer sync, sharing, and hosted deployments. Lives in spikes-hosted/.

Development

CLI

cd cli

cargo build --release cargo test # 160+ tests cargo run -- --help

Widget

cd widget

Edit src/spikes.js

Test by running: spikes serve from the project root

Widget Regression Tests

CI suite that catches the silent-data-loss bug class (e.g., widget loaded on a non-allowe

Only the beginning is shown; read the rest in the repo

Spikes

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Zendesk

README from the maker

/ Spikes

What Is This?

Quick Start

1. Install the CLI

Or: cargo install spikes

2. Initialize your project

spikes init --self-host # Opt out — scaffold a self-hosted config instead

3. Add the widget to your HTML

4. Collect and use feedback

CLI Commands

List all projects you own (with spike_count + last_activity)

GET /me/projects/:key/spikes

List spikes for one of your projects (paginated, filterable: page, per_page,

filter_page, filter_rating, filter_resolved)

PATCH /me/projects/:key/spikes/:id

Toggle the resolved flag on one spike

POST /projects

Create a new project (user bearer only)

Single-line variant (copy-paste friendly)

AI Agent Integration

or: spikes mcp serve # If you have the CLI installed

MCP Server — 16 Tools

API Keys

Agent-Tier Billing

Context Exports

Discovery

GitHub Action

Widget Attributes

Architecture

Development

CLI

Widget

Edit src/spikes.js

Test by running: spikes serve from the project root

Widget Regression Tests

Toggle the `resolved` flag on one spike