Splera

io.github.sohaibtPublished by GitHub account sohaibtv0.1.1Updated Oct 28, 2026

A/B testing for vibe coders: create, track, and ship experiments from your AI coding agent.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Splera's local MCP server lets an AI coding agent create, track and ship A/B testing experiments from the editor.

What you can do
  • Create and manage A/B testing experiments from the AI coding agent.
  • Track experiment status and results as work progresses.
  • Ship (conclude or roll out) experiments once a decision is made.
  • No individual tools are documented in the supplied listing, so exact operations are not described.
When to use it
Useful when you run A/B tests and want your coding agent to set up, monitor and conclude experiments without leaving the editor, especially for small teams or solo developers doing rapid iteration.
Requirements
Runs as a local stdio process, installed from the npm package splera-mcp (Node.js runtime). Requires a Splera account and an API key supplied in the SPLERA_API_KEY environment variable. Network access to the Splera API; SPLERA_API_URL can override the base URL for local or staging testing. Desktop client only.
Before you install
The API key in SPLERA_API_KEY is a credential granting access to your Splera account; keep it out of shared configs and logs. The server can create, change and ship experiments, so agent actions may alter live tests and the traffic they affect. Experiment data is sent to the Splera service.

Installation

In SourceWeft

  1. Open Splera 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.1.1LatestSep 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.