SpikeMe

io.github.isaacviannadevPublished by GitHub account isaacviannadevv0.5.6Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

SpikeMe is a local MCP server that analyzes a repository's technology stack and produces grounded, time-boxed spike decision documents for an AI assistant.

What you can do
Analyze a repository's stack to identify the technologies in use and produce a grounded assessment of it. Generate time-boxed spike decision documents based on that analysis. Optionally authenticate with a SpikeMe access token to unlock the document-generation tool, while stack analysis works without it.
When to use it
Useful when you want an assistant to inspect an existing codebase's technology stack and turn it into a short, time-boxed spike or decision document before committing to an approach.
Requirements
Runs as a local process via the npm package spikeme-mcp over stdio, so a Node.js runtime is needed. The optional SPIKEME_TOKEN environment variable enables the generate_spike tool, or you can run the package's login command once; analyze_stack works without it.
Before you install
The optional SPIKEME_TOKEN is a secret credential; keep it out of shared configuration and logs. The server reads repository contents to analyze the stack, so consider what code it can access. Document generation may send data to the SpikeMe service when a token is used.

Installation

In SourceWeft

  1. Open SpikeMe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.6LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.