Spikes

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "spikes": {
      "command": "npx",
      "args": [
        "-y",
        "spikes"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

/ 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

Terminal

curl -fsSL https://spikes.sh/install.sh | sh
# Or: cargo install spikes

2. Initialize your project

bash

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

bash

spikes inject ./mockups/        # Injects widget script tag (uses configured endpoint)
spikes serve                    # http://localhost:3847

4. Collect and use feedback

bash

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 <id>             # 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 <id>`	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 <dir>`	Add/remove widget from HTML files (`--endpoint <url>` 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 <dir>`	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 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):

bash

# 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/<spike_id>

# 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.

Terminal

npx spikes-mcp            # Zero-install MCP server — just works
# or: spikes mcp serve    # If you have the CLI installed

MCP Server — 9 Tools

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

Tool	Purpose
`get_spikes`	List feedback with filters (page, rating, unresolved)
`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

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

bash

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:

bash

spikes auth create-key --name "my-agent"   # → sk_spikes_...
spikes auth list-keys                       # See all keys
spikes auth revoke-key <key_id>            # 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:

bash

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:

server.ts

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

Discovery

llms.txt — All 9 MCP tools, parameters, agent quickstart
agents.md — Machine-readable landing page for agents
Smithery — 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.

yaml

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:

html

<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:

html

<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">
</script>

Self-hosting — point to your own backend:

html

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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Spikes

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "spikes": { "command": "npx", "args": ["-y", "spikes"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/spikes?style=directory)](https://allmcps.com/mcp/spikes)

HTML Embed

<a href="https://allmcps.com/mcp/spikes"><img src="https://allmcps.com/api/badge/spikes?style=directory" alt="Spikes on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Spikes →Install in Claude Desktop Install in Cursor Install in VS Code

Spikes

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "spikes": {
      "command": "npx",
      "args": [
        "-y",
        "spikes"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

/ 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

Terminal

curl -fsSL https://spikes.sh/install.sh | sh
# Or: cargo install spikes

2. Initialize your project

bash

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

bash

spikes inject ./mockups/        # Injects widget script tag (uses configured endpoint)
spikes serve                    # http://localhost:3847

4. Collect and use feedback

bash

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 <id>             # 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 <id>`	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 <dir>`	Add/remove widget from HTML files (`--endpoint <url>` 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 <dir>`	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:

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

bash

# 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/<spike_id>

# 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.

Terminal

npx spikes-mcp            # Zero-install MCP server — just works
# or: spikes mcp serve    # If you have the CLI installed

MCP Server — 9 Tools

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

Tool	Purpose
`get_spikes`	List feedback with filters (page, rating, unresolved)
`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

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

bash

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:

bash

spikes auth create-key --name "my-agent"   # → sk_spikes_...
spikes auth list-keys                       # See all keys
spikes auth revoke-key <key_id>            # 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:

bash

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:

server.ts

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

Discovery

llms.txt — All 9 MCP tools, parameters, agent quickstart
agents.md — Machine-readable landing page for agents
Smithery — 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.

yaml

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:

html

<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:

html

<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">
</script>

Self-hosting — point to your own backend:

html

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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Spikes

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "spikes": { "command": "npx", "args": ["-y", "spikes"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/spikes?style=directory)](https://allmcps.com/mcp/spikes)

HTML Embed

<a href="https://allmcps.com/mcp/spikes"><img src="https://allmcps.com/api/badge/spikes?style=directory" alt="Spikes on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Featured

AllMCPs Server

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Spikes →Install in Claude Desktop Install in Cursor Install in VS Code