# Roamer MCP [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/mathismeadows/roamer-mcp-plugin  
**GitHub Stars:** 0  
**npm Downloads (last month):** 369  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/roamer-mcp

## Description
Project registry, behavioral specs, and engineering threads for AI coding agent workflows.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "roamer-mcp": {
    "command": "npx",
    "args": ["-y","@mathismeadows/roamer-device-auth"]
  }
}
```

## Documentation

## What Roamer MCP MCP server does

Roamer MCP MCP server provides a Claude Code plugin for working with three parts of the Roamer system: a project registry, a behavioral specification database, and engineering threads. The plugin exposes eleven workflows as slash commands, while also allowing Claude to invoke a workflow when the conversation matches its purpose.

The session-oriented commands help maintain continuity. `/roamer:orient` prepares a start-of-session briefing from the registry and open threads, while `/roamer:breadcrumb` records an end-of-session checkpoint with registry and thread updates. Feature and bug work follow separate gated processes: `/roamer:feature` runs a seven-step workflow, and `/roamer:bug` runs an eight-step workflow.

Other commands cover specification review, thread maintenance, release-note drafting, and authentication state. `/roamer:spec-audit` checks specification coverage, `/roamer:spec-check` runs a hygiene checklist, and `/roamer:thread-scrub` guides review of the open-thread backlog. `/roamer:release-notes` drafts internal and external notes for a selected date window and is review-only. Login, logout, and status commands manage the identities cached for each client.

## How it works

The repository is a distribution package rather than the implementation of the Roamer backend. Its `.mcp.json` configuration runs `npx -y @mathismeadows/roamer-device-auth`. That device-auth component authenticates against RoamerMcp’s OAuth server and bridges the local stdio connection to the hosted MCP endpoint.

On first use, Claude Code prompts the user to authenticate through a per-user Entra ID OAuth flow. The plugin workflows then use the same MCP-backed capabilities exposed by RoamerMcp.

## Setup and configuration

Install the marketplace entry and plugin from Claude Code:

```text
/plugin marketplace add mathismeadows/roamer-mcp-plugin
/plugin install roamer@roamer
```

After installation, authenticate when Claude Code requests it. New accounts are provisioned automatically at first login, but the project currently requires manual approval before a new account can use RoamerMcp tools. Access is therefore subject to the documented beta gate.

No environment variables or manually supplied access tokens are documented for this package. The repository contains the plugin manifest, marketplace metadata, MCP configuration, and workflow skills; it does not contain server implementation or test code.

## Tools and capabilities

Roamer MCP MCP server is suited to teams that want coding agents to begin with current project context and finish by recording relevant changes. Its documented workflows support:

- Session orientation and end-of-session checkpoints
- Gated feature implementation and bug-fix processes
- Specification coverage and hygiene reviews
- Guided cleanup of open engineering threads
- Review-only release-note drafts for a date range
- Per-client identity switching, logout, and status inspection

The package is specifically documented for Claude Code.

_Full upstream README: https://allmcps.com/mcp/roamer-mcp/readme_