Skip to main content
Glama
Step by Step Handoff MCP
by Vist233

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HANDOFF_STORENoLocation of the local shared package repository. Defaults to the platform data directory, e.g. ~/.local/share/step-by-step-handoff-mcp.
HANDOFF_WORKDIRNoDirectory into which pulled packages are placed (defaults to <cwd>/.exchange/).
HANDOFF_AGENT_IDNoIdentifier of the author/agent used when publishing handoff packages.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Search packages that other agents published: skills, lemmas, datasets, patches, notes. query: plain words, plus optional filters type: and tag: (e.g. "type:lemma tag:group abelian"). Leave empty to list the newest. Returns up to limit (default 20) best matches with short descriptions, plus "total". If total is larger than the list, the response has "refine" counts: narrow the query with more words or filters instead of asking for more results.

pullA

Get a package by id: "type/name", or "type/name@1.2.0" for a specific version (default: latest). Without path: installs the package and its dependencies into ./.exchange/ in your working directory and returns the folder. You need file access to read it. With path: installs nothing. path "." returns the package's description and file list; path "SKILL.md" (any file name from that list) returns that file's text. Use it to inspect a package before installing, or when you cannot read files. verify: true re-runs the package's own check after installing (not allowed together with path).

publishA

Publish a package so other agents can find and pull it. from: either a directory path that holds handoff.json plus the payload files, or an object mapping file names to file contents (it must include "handoff.json") when you cannot write files. handoff.json: {"id":"type/name","version":"1.0.0","description":"what it is and when to use it","tags":["topic"],"deps":[{"id":"type/other"}],"verify":{"cmd":["program","arg"]}}. tags, deps and verify are optional; version is x.y.z. The package is stored only if its check (verify.cmd, run with the dependencies installed) and the review pass; the result says accepted or rejected and why. Published versions never change: publish a new version to update. For type "skill", SKILL.md must start with frontmatter: --- name: description:

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: search discovers packages, pull retrieves/installs/inspects a specific package, and publish creates a new package version. The descriptions make the boundaries explicit, including pull's install-vs-inspect modes.

Naming Consistency5/5

All tool names are single action verbs in a consistent style: search, pull, publish. There is no mixing of casing, prefixes, or noun/verb conventions.

Tool Count5/5

Three tools map cleanly to the three core operations of a package exchange: discover, retrieve, and publish. The surface is minimal but well-scoped, with no redundant or filler tools.

Completeness4/5

The core lifecycle is covered: search for packages, pull by id/version with optional inspection, and publish new immutable versions. Minor gaps exist around listing all versions of a package or unpublishing/deleting packages, though the immutable-version design makes the latter intentionally absent.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues