Roamer MCP

com.mathismeadowsPublished by mathismeadows.comOfficial publisherv2.0.1Updated Oct 29, 2026

Hosted MCP server and Agent Skills for specs, engineering threads, and project memory.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Hosted MCP server for a project registry, behavioral spec database and engineering threads, with optional Claude Code workflow commands.

What you can do
  • Read and write project registry entries, behavioral specs, engineering threads, blockers and session notes through the hosted server.
  • Run guided workflows for session orientation, end-of-session checkpoints, gated feature and bug-fix steps, spec coverage audits and spec hygiene checks.
  • Review and dispose of the open-thread backlog, and draft internal or external release notes for a date window.
  • Export a snapshot of specs, threads and the project brain to local files in a chosen format.
  • Sign in, switch identity, check the signed-in identity, or sign out of the Roamer connection.
When to use it
Useful when a team keeps its project specs, engineering threads and project memory in Roamer and wants an assistant to read and update them during development sessions, or to run structured feature, bug-fix, audit and release-note workflows.
Requirements
A remote hosted endpoint; no Node.js or local install. OAuth sign-in through the browser on first use, and re-authentication to switch accounts. The optional plugin is installed through a Claude Code plugin marketplace. New accounts are provisioned automatically but currently need manual approval before tools are enabled.
Before you install
The server receives the arguments you pass to workflows and the Roamer content you read or write, including projects, specs, threads, blockers and session notes. Workflows can update the registry and threads, and export writes snapshots to local files. Sign-in is OAuth, so the password is not handled by the plugin. Keep only one Roamer connection per client to avoid duplicate servers.

Installation

In SourceWeft

  1. Open Roamer MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.mathismeadows%2Froamer-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "roamer": {
      "type": "http",
      "url": "https://roamer-mcp.mathismeadows.com/mcp"
    }
  }
}

README

roamer-mcp-plugin

[Listed on mcpservers.org]

Distributable Claude Code plugin for Roamer MCP — the Roamer project registry, behavioral spec database, and engineering threads MCP server. Learn more at roamermcp.mathismeadows.com.

The plugin is an optional extra on top of the hosted Roamer MCP server (https://roamer-mcp.mathismeadows.com/mcp). Connecting to that server on its own already gives every tool and workflow; installing this plugin adds the following workflows as slash commands. 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:thread-scrub — guided review and disposition of the open-thread backlog, on demand
  • /roamer:release-notes — draft Internal/External release notes for a date window, review-only
  • /roamer:export — save a snapshot of specs, threads and the brain to local files, in a format you choose
  • /roamer:login — sign in, or switch which identity this session uses
  • /roamer:logout — sign this session's Roamer connection out
  • /roamer:status — see which identity this connection is signed in as

Install

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

The plugin connects to the hosted server over HTTP — no Node.js or local install. On first use, sign in with /mcp: select the plugin's Roamer server and follow the browser sign-in. To switch accounts later, use /mcp → Re-authenticate, or Clear authentication to sign out.

Keep one Roamer connection per client. If you've also added Roamer as a claude.ai connector or with claude mcp add, Claude Code treats a plugin server and a connector on the same URL as duplicates and ranks the plugin's first. Turn off any other Roamer server in /mcp so it's clear which one a session is using.

Data & privacy

The plugin connects only to the hosted Roamer MCP server at https://roamer-mcp.mathismeadows.com/mcp. It sends that server the arguments you give a workflow (for example a project name or a date window) and the Roamer content you read or write through it: projects, specs, threads, blockers and session notes. You sign in with OAuth in your browser; the plugin never sees or stores your password. The plugin runs no local code: it is only markdown skills and a server address. See the privacy policy for how Roamer handles your data.

Status

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 Roamer MCP's tools (a beta access gate); you'll be notified once yours is enabled.

Structure

  • .claude-plugin/plugin.json — plugin manifest
  • .claude-plugin/marketplace.json — self-referential marketplace entry
  • .mcp.json — the hosted Roamer MCP server over HTTP, under the server name mcp
  • skills/ — the workflow commands above; each one reads its current instructions from the server

This repo is distribution-only — it has no server code, no tests, and no relation to Roamer MCP's internal architecture beyond consuming its public MCP endpoint.

Source: README.md at commit 020df5c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v2.0.1LatestOct 29, 2026
  2. v2.0.0Oct 15, 2026
  3. v1.5.0Oct 12, 2026
  4. v1.2.5Sep 16, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.