BRICO feature memory

io.github.ScienceWerx-IncPublished by GitHub account ScienceWerx-Incv0.2.0Updated Oct 29, 2026

Find features you built in other projects, see how they fit this one, and reuse them.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

BRICO feature memory lets a coding agent find features you built in other projects, judge how well they fit the current one, and reuse them.

What you can do
  • Search your indexed projects for features you have already built
  • Compare a found feature against the project you are working in and rate how well it fits
  • Reuse or wire an existing feature into the current codebase through the coding agent
  • Index a local project directory so its features become searchable memory
When to use it
Useful when you work across several codebases and want your coding agent to reuse code you already wrote instead of rebuilding it, or to check whether an existing feature fits a new project.
Requirements
Runs locally over stdio via the npm package bricowerx (Node.js, typically through npx). Needs a BRICO Builder invite token, supplied as the BRICO_TOKEN environment variable or stored by running the brico login command. Projects must be indexed first with the brico index command.
Before you install
The server asks for a BRICO Builder invite token (BRICO_TOKEN); treat it as a secret and prefer the login command over putting it in plain configuration. Indexing a project sends its feature information to BRICO, so avoid indexing code you cannot share. The agent can change your codebase when it wires in a reused feature.

Installation

In SourceWeft

  1. Open BRICO feature memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

BRICO releases

Release binaries for BRICO: your feature memory. BRICO finds the features you've built in your other projects, tells you how well each fits the project you're in, and lets your coding agent wire it in.

This repository holds release downloads only. Docs: https://www.bricowerx.com

Install

sh
npm i -g bricowerx# orcurl -fsSL https://github.com/ScienceWerx-Inc/brico_release/releases/latest/download/install.sh | sh

Use it in your coding agent (MCP)

sh
brico login bt_…                               # your BRICO Builder invite tokenbrico index ~/code/an-old-project              # remember its featuresclaude mcp add brico -- npx -y bricowerx mcp   # Claude Code

Cursor, in ~/.cursor/mcp.json:

json
{ "mcpServers": { "brico": { "command": "npx", "args": ["-y", "bricowerx", "mcp"] } } }

Every release includes SHA256SUMS.txt; the installers verify downloads against it.

MCP registry

server.json is the server's MCP registry entry, io.github.ScienceWerx-Inc/brico. After each npm release, copy it from the source repository and run Actions → MCP registry → Run workflow.

Source: README.md at commit 7a124c5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestOct 29, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

Other Memory integrations