Project registry, behavioral specs, and engineering threads for AI coding agent workflows.
Distributable Claude Code plugin for RoamerMcp — the Roamer project registry, behavioral spec database, and engineering threads MCP server. Learn more at roamermcp.mathismeadows.com.
Installing this plugin gives you nine workflows backed by the same tools RoamerMcp exposes over MCP. Each is a slash command, but Claude can also invoke one on its own when the conversation calls for it — you don't have to type the command yourself:
/roamer:orient — start-of-session briefing (project registry + open threads)/roamer:breadcrumb — end-of-session checkpoint (registry + thread updates)/roamer:feature — seven-step gated feature workflow/roamer:bug — eight-step gated bug-fix workflow/roamer:spec-audit — spec coverage audit/roamer:spec-check — hygiene checklist/roamer:login — switch which identity this client is signed in as/roamer:logout — clear a client's cached identity so it signs in fresh next time/roamer:status — see which identities are cached and active, per client/plugin marketplace add mathismeadows/roamer-mcp-plugin
/plugin install roamer@roamer
On first use, Claude Code will prompt you to authenticate against the hosted RoamerMcp endpoint (per-user Entra ID login via OAuth) — no manual token setup required.
This repo is public — install directly with the commands above. New accounts are provisioned automatically on first login, but currently need manual approval before they can use RoamerMcp's tools (a beta access gate); you'll be notified once yours is enabled.
.claude-plugin/plugin.json — plugin manifest.claude-plugin/marketplace.json — self-referential marketplace entry.mcp.json — spawns scripts/roamer-bridge.sh via ${CLAUDE_PLUGIN_ROOT}scripts/ — the same local stdio bridge (authenticates against RoamerMcp's own OAuth server — a device-code flow for Safari-default machines, a lighter loopback redirect for everything else — via the published @mathismeadows/roamer-device-auth npm package, invoked via npx) used by RoamerMcp's own dev setupskills/ — the six workflow commands aboveThis repo is distribution-only — it has no server code, no tests, and no relation to RoamerMcp's internal architecture beyond consuming its public MCP endpoint.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @mathismeadows/roamer-device-authMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-mathismeadows-roamer-mcp": {
"command": "npx",
"args": [
"-y",
"@mathismeadows/roamer-device-auth"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@mathismeadows/roamer-device-authnpmRoamer MCP works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.