Campfyrr

io.github.sarkarsPublished by GitHub account sarkarsv0.1.1Updated Oct 27, 2026

Campfyrr, shared team memory for Claude Code

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Campfyrr is a remote MCP server giving Claude Code a shared team memory: session briefs, area briefs, news and handoffs across developers.

What you can do
  • Record and share team work state: assumptions, logged work, decisions, work started and handoffs
  • Receive a session brief at start with tasks, teammates' updates, standing rules and decisions
  • Get an area brief on the first read or edit in each part of the code, covering work in progress and dropped approaches
  • Get news during a request about answered assumptions, landed work and clashing decisions
  • Attach reasons for each change to commits and link them from the pull request
When to use it
Useful for teams where several developers run Claude Code on the same codebase and need sessions to know what others are changing, deciding or assuming, and for handing a half-finished session to a teammate. Not a replacement for a tracker, CI or test runner.
Requirements
A remote endpoint at campfyrr.vercel.app with OAuth sign-in required. A Campfyrr account and a token created after signing in, pasted during install; Claude Code stores it in secure storage. Installed as a Claude Code plugin from the sarkars/campfyrr marketplace, or via the setup command on the connect page.
Before you install
Requires an account token that grants access to your team's shared memory; keep it private and change it through the plugin configuration if needed. The service records work state, decisions and handoffs, and shares them with teammates and, via links, the wider company. It states it never stores your code. Paid tiers apply after early access: free for one person, $9 per developer per month for teams. Installing both the plugin and the earlier hook setup duplicates hooks in Claude settings.

Installation

In SourceWeft

  1. Open Campfyrr 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/io.github.sarkars%2Fcampfyrr/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": {
    "campfyrr": {
      "type": "http",
      "url": "https://campfyrr.vercel.app/api/mcp"
    }
  }
}

README

Campfyrr for Claude Code

Campfyrr, shared team memory for Claude Code.

[team memory: Campfyrr]

Every teammate's sessions know what the others are changing, what was decided and what was assumed, before they touch the code. The rest of the company follows the work from a link. Campfyrr never stores your code.

Install

  1. Sign in at https://campfyrr.vercel.app/connect?ref=github and create a token.
  2. Run claude plugin marketplace add sarkars/campfyrr.
  3. Run claude plugin install campfyrr@campfyrr.
  4. Paste the token when the install asks for it.

Or paste the one command on https://campfyrr.vercel.app/connect?ref=github into a terminal. It sets up the same hooks and MCP server without the plugin.

What it answers

What it does

  • A brief at session start: your tasks, teammates' updates, the rules and the decisions that stand.
  • An area brief on the first read or edit in each part of the code: work in progress there, decisions that apply, what was tried and dropped.
  • News at each request: answers to your agent's assumptions, work it waited on that landed, decisions that clashed.
  • A handoff when a session stops half-way, and the reasons for each change, linked from the pull request.

It doesn't run agents, run tests, or replace your tracker or CI. Free during early access; then free for one person, $9 per developer a month for teams, and business teammates free. See what your agent sees · Pricing · Trust · How it compares

The plugin

Shared team memory for Claude Code. Every teammate's sessions know what the others are changing, what was decided and what was assumed, before they touch the code. The rest of the company follows the work from a link. Campfyrr never stores your code.

Install

claude plugin marketplace add sarkars/campfyrrclaude plugin install campfyrr@campfyrr

When asked, paste your token from https://campfyrr.vercel.app/connect (sign in, then create a token). Claude Code keeps it in secure storage. To change it later: /plugin, then Campfyrr, then Configure options.

What it adds

  • A session brief when a session starts: what changed since your last session, open questions, the team's rules.
  • Area briefs the first time a session reads or edits a part of the code: work in progress there, decisions that apply, what was tried.
  • News during the work: answers to its questions, work it waited on that landed, decisions that clashed or were settled.
  • Handoffs when a session stops, and reasons for each change on commit.
  • The Campfyrr tools (state_assumption, log_work, log_decision, start_work, hand_off and more), and a skill that tells Claude how to use them.

Free for one person. Teams: $9 per developer a month, free during early access.

If you installed Campfyrr earlier with the paste from /connect, you don't need both: remove the Campfyrr hooks from ~/.claude/settings.json, or skip the plugin.

Source: README.md at commit eff676f

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

2
  1. v0.1.1LatestOct 23, 2026
  2. v0.1.0Oct 21, 2026

Score

85% 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