Analyze your repo's stack and generate grounded, time-boxed spike decision docs.
Connect Runs on your machine
claude mcp add spikeme -e SPIKEME_TOKEN=<SPIKEME_TOKEN> -- npx -y [email protected]{
"mcpServers": {
"spikeme": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SPIKEME_TOKEN": "<SPIKEME_TOKEN>"
}
}
}
}{
"mcpServers": {
"spikeme": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SPIKEME_TOKEN": "<SPIKEME_TOKEN>"
}
}
}
}{
"servers": {
"spikeme": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"SPIKEME_TOKEN": "<SPIKEME_TOKEN>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
SPIKEME_TOKENOptional, secret | Optional SpikeMe access token to enable generate_spike (or run `npx spikeme login` once). analyze_stack works without it. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 9 Aug 2026 |
| Last updated | 9 Aug 2026 |
| Registry name | io.github.isaacviannadev/spikeme |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.