
Mcp Gera Skills
io.github.geraservicesukPublished by GitHub account geraservicesukv0.1.0Updated Oct 24, 2026
GeraSkills MCP — search and install robot capability packs on behalf of an operator.
Overview
Lets an assistant search and install robot capability packs from the GeraSkills backend on behalf of an operator.
- What you can do
- This local MCP server connects an assistant to the GeraSkills backend, where robot capability packs (skills) are catalogued. It exposes tools for searching that catalogue and for installing a skill, with installation performed on behalf of a named operator. The manifest does not list individual tool names beyond install_skill.
- When to use it
- Worth adding when you want an assistant to look up available robot capability packs and install them for a specific operator account, rather than browsing the catalogue by hand. It is a narrow, single-purpose server, so it is not useful if you do not work with GeraSkills skills.
- Requirements
- Runs as a local process over stdio, installed from the npm package @gera-services/mcp-gera-skills, so Node.js is needed. It requires the environment variable GERA_USER_TOKEN, a JWT for the operator the agent acts on behalf of, and optionally GERASKILLS_API_URL, which defaults to the GeraSkills backend URL. Network access to that backend is required. Desktop only.
Installation
In SourceWeft
- Open Mcp Gera Skills in the dashboard and add it to a workspace.
- 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
0Version history
1- v0.1.0LatestSep 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.