mcpField
S
SpikeMe

SpikeMe

Local
spikeme.ioDeveloper Tools
RepositoryVisit website

About SpikeMe

Analyze your repo's stack and generate grounded, time-boxed spike decision docs

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "isaacviannadev-spikeme": {
      "command": "npx",
      "args": [
        "-y",
        "spikeme-mcp"
      ],
      "env": {
        "SPIKEME_TOKEN": "<SPIKEME_TOKEN>"
      }
    }
  }
}
Run commandnpx -y spikeme-mcp
Environment variables to set
SPIKEME_TOKENSecretOptional SpikeMe access token to enable generate_spike (or run `npx spikeme login` once). analyze_stack works without it.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmspikeme-mcp0.5.6

Tools

3

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
pathstringNoRepo directory to analyze (default: current working directory)

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.