Other · Local MCP server
SpikeMe
Analyze your repo's stack and generate grounded, time-boxed spike decision docs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.isaacviannadev/spikeme- Version
- 0.5.6
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-09
- Updated
- 2026-08-09
- Publisher
- isaacviannadev (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/isaacviannadev) · how
- Website
- spikeme.io/docs/mcp
- Repository
- github.com/isaacviannadev/Package-spike
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | spikeme-mcp | 0.5.6 | stdio |
How to connect SpikeMe
SpikeMe runs locally from a Node.js package published to the npm registry: spikeme-mcp version 0.5.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y spikeme-mcp@0.5.6. It reads the environment variable SPIKEME_TOKEN (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"spikeme": {
"command": "npx",
"args": [
"-y",
"spikeme-mcp@0.5.6"
],
"env": {
"SPIKEME_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| SpendAgents are not bots. PayClaw proves it - then lets them pay. Badge + Spend on existing Visa rails. | Local · stdio |
| SpendictA performance marketer's run/fix/kill verdict for AI agents - ad creative, campaigns, targeting. | Remote · HTTPLive check: ✗ no handshake |
| SpendNodAI agent spending controls. Set limits, blocklists, and caps. Approve transactions from your phone. | Remote · HTTPLive check: sign-in required |
| Sphere MarketplaceOne agent sells work, another buys it; delivery passes a gate and comes with a verifiable receipt. | Remote · HTTPLive check: ✓ handshake |
| SpikesUI feedback for AI-assisted building. Click elements, rate them, agents triage via MCP. | Local · stdio |
| SpikeshRead Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority. | Remote · HTTPLive check: ✓ handshake |
| SpinesAccess book collections, reading lists, and bookshelf recognition from AI assistants. | Local · stdio |
| SpinGrasEU AI Act Article 4 (AI literacy) readiness check and intro booking with SpinGras, Amsterdam. | Remote · HTTPLive check: ✓ handshake |