Mcp Gera Clone

io.github.geraservicesukPublished by GitHub account geraservicesukv0.1.1Updated Oct 30, 2026

GeraClone MCP — discover expert clones, check operator's clone status, start expert chats (consent).

Overview

AI-generated overview

Local MCP server for GeraClone that lets an assistant find expert clones, check an operator's clone status and start consent-based chats with experts.

What you can do
  • Discover expert clones available on the GeraClone backend
  • Check the operator's own clone status and corpus summary
  • Start a chat with an expert, with consent handled by the service
  • Connect to a configurable GeraClone backend URL
When to use it
Useful when you work with the GeraClone platform and want an assistant to look up expert clones, review your own clone and corpus status, or open an expert conversation without leaving the chat.
Requirements
Runs as a local stdio process, installed from the npm package @gera-services/mcp-gera-clone (Node.js). Needs network access to the GeraClone backend, set via GERACLONE_API_URL (defaults to the hosted clone.gera.services backend). A GERA_USER_TOKEN JWT is required for the expert chat, clone status and corpus summary tools.
Before you install
Requires a GERA_USER_TOKEN JWT that identifies the operator the agent acts for; treat it as a secret and keep it out of shared configs. Starting an expert chat sends requests to the GeraClone backend and involves consent, so confirm before the assistant initiates conversations. Clone status and corpus summary expose information about the operator's own data.

Installation

In SourceWeft

  1. Open Mcp Gera Clone 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.