Roamer MCP server
{
"mcpServers": {
"mathismeadows-roamer": {
"command": "npx",
"args": [
"-y",
"@mathismeadows/roamer-device-auth@latest"
]
}
}
}{
"mcpServers": {
"mathismeadows-roamer": {
"command": "npx",
"args": [
"-y",
"@mathismeadows/roamer-device-auth@latest"
]
}
}
}{
"mcpServers": {
"mathismeadows-roamer": {
"command": "npx",
"args": [
"-y",
"@mathismeadows/roamer-device-auth@latest"
]
}
}
}{
"servers": {
"mathismeadows-roamer": {
"command": "npx",
"args": [
"-y",
"@mathismeadows/roamer-device-auth@latest"
]
}
}
}{
"mcpServers": {
"mathismeadows-roamer": {
"command": "npx",
"args": [
"-y",
"@mathismeadows/roamer-device-auth@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @mathismeadows/roamer-device-authversion 1.3.1
What it does
Roamer exposes a project registry, behavioral specification database, and engineering thread management for AI coding agent workflows. It's for teams using Claude for coordinated AI-assisted development work that needs to track project state, specifications, and ongoing engineering discussions.
- Start a coding session with a project briefing that includes the current registry and open engineering threads.
- Run a structured feature development workflow with seven gated steps to guide implementation from spec to completion.
- Audit specification coverage or run a hygiene checklist to ensure engineering documentation meets standards.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.