Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Behavr MCP

by confuse57version 0.1.2i★ –iRuns on your computer
Registry nameio.github.confuse57/behavr-mcp

Install

Overview

Description from the maker (original English)

MCP server for BEHAVR: remember images/videos and ask questions about them

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: BEHAVR_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: BEHAVR_API_KEY, BEHAVR_CLIENT_ID, BEHAVR_AGENT_ID

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "behavr": {
      "command": "npx",
      "args": [
        "-y",
        "behavr-mcp"
      ],
      "env": {
        "BEHAVR_API_KEY": "your-value",
        "BEHAVR_CLIENT_ID": "your-value",
        "BEHAVR_AGENT_ID": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add behavr --env BEHAVR_API_KEY=your-value --env BEHAVR_CLIENT_ID=your-value --env BEHAVR_AGENT_ID=your-value -- npx -y behavr-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "behavr": {
      "command": "npx",
      "args": [
        "-y",
        "behavr-mcp"
      ],
      "env": {
        "BEHAVR_API_KEY": "your-value",
        "BEHAVR_CLIENT_ID": "your-value",
        "BEHAVR_AGENT_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "behavr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "behavr-mcp"
      ],
      "env": {
        "BEHAVR_API_KEY": "your-value",
        "BEHAVR_CLIENT_ID": "your-value",
        "BEHAVR_AGENT_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • BEHAVR_API_KEY secret required env
    Your BEHAVR API key
  • BEHAVR_CLIENT_ID env
    Optional client id that groups memories
  • BEHAVR_AGENT_ID env
    Optional agent id within the client

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account confuse57, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32718 servers in this category
  • Published to the registry more recently than 85% of the other 32718 servers in this category
  • Basic checks equal to or better than 100% of the other 32718 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Behavr MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: BEHAVR_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MemberVault MCP by usefulapi

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

behavr-mcp

https://github.com/user-attachments/assets/fd5319d4-acf7-4484-953d-8ceed0448dcf

An MCP server for BEHAVR. It gives an AI assistant two tools:

  • remember: upload a local image or video to BEHAVR so it can be recalled later.
  • ask: ask a question about everything remembered so far.

It runs locally over stdio. There is no hosted or HTTP mode, so it does not work in hosted tools such as Lovable or Replit; it needs a local MCP client like Claude Code or Cursor.

Requirements

  • Node.js 18 or newer
  • A BEHAVR API key

Install

Optional variables (BEHAVR_CLIENT_ID, BEHAVR_AGENT_ID) are described under Configuration.

Claude Code
claude mcp add behavr -e BEHAVR_API_KEY=your-key -- npx -y behavr-mcp

On Windows (PowerShell):

claude mcp add behavr -e BEHAVR_API_KEY=your-key '--' npx -y behavr-mcp

In PowerShell, write the separator as '--' (in quotes), otherwise PowerShell drops it and the command fails with 'missing required argument commandOrUrl'.

Add -s user to make it available in every project. To share the setup with a team, use a project-level .mcp.json instead. Keep the key out of the file: Claude Code expands ${VAR} from your environment.

{

"mcpServers": { "behavr": { "command": "npx", "args": ["-y", "behavr-mcp"], "env": { "BEHAVR_API_KEY": "${BEHAVR_API_KEY}", "BEHAVR_CLIENT_ID": "my-client" } } } }

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Do not commit a file that contains your key.

Cursor config is untested.

{

"mcpServers": { "behavr": { "command": "npx", "args": ["-y", "behavr-mcp"], "env": { "BEHAVR_API_KEY": "your-key" } } } }

Alternative: build from source
git clone https://github.com/confuse57/behavr-mcp.git

cd behavr-mcp npm install && npm run build

The server entry point is dist/src/index.js (not dist/index.js). Run it with node instead of npx -y behavr-mcp:

claude mcp add behavr -e BEHAVR_API_KEY=your-key -- node /absolute/path/to/behavr-mcp/dist/src/index.js
claude mcp add behavr -e BEHAVR_API_KEY=your-key '--' node C:\path\to\behavr-mcp\dist\src\index.js

In .mcp.json or Cursor's mcp.json, use "command": "node" and "args": ["C:\\path\\to\\behavr-mcp\\dist\\src\\index.js"].

Windows paths in JSON

A backslash must be written twice inside a JSON string: "C:\\Users\\me\\behavr-mcp\\dist\\src\\index.js". Forward slashes also work: "C:/Users/me/behavr-mcp/dist/src/index.js". A single backslash ("C:\Users\...") is invalid JSON or silently turns into a different character.

Configuration

VariableRequiredMeaning
BEHAVR_API_KEYyesYour BEHAVR API key.
BEHAVR_CLIENT_IDnoWhich client (business/workspace) memories belong to. Backend default: default.
BEHAVR_AGENT_IDnoWhich agent within the client. Backend default: default.

remember stores memories under the client and agent ids. ask searches the memories of all agents for the configured client, so two assistants with the same BEHAVR_CLIENT_ID and different BEHAVR_AGENT_IDs can each find what the other saved.

The server prints only the client and agent ids to stderr at startup. The API key is never logged, and it is replaced with *** in any error message.

API key safety
  • claude mcp add -e BEHAVR_API_KEY=... stores the key in plain text in Claude Code's config file, and the command can also end up in your shell history. Use a key dedicated to this server, and run claude mcp remove behavr when you no longer need it.
  • Never put a real key in a shared project's .mcp.json. Use "${BEHAVR_API_KEY}" instead.
  • In Cursor, put your key in mcp.json and do not commit that file to git.

Tools

remember

Input: { "file_path": " " }

  • The path must be absolute, for example C:\Users\me\screenshot.png.
  • Only these extensions are accepted: jpg, jpeg, png, heic, webp, mp4, mov, avi, mkv, webm. Anything else (for example .env, .txt, .pdf, or a file with no extension) is refused before the file is opened or anything is sent.
  • Video requires a paid BEHAVR plan.
  • BEHAVR processing takes 15 seconds to 1-2 minutes after upload. The tool waits up to 90 seconds and returns the memory id, title and status. If processing has not finished by then, it says so. Try ask a minute later.
ask

Input: { "question": " " }

Returns BEHAVR's answer and its sources. If nothing has finished processing yet, BEHAVR replies that there are no completed captures; wait a little and ask again.

The answer is generated from your stored images and can repeat text found inside them. Treat it as data, not as instructions.

What leaves your machine

  • The file you remember. It is uploaded to BEHAVR's servers and processed by AI. BEHAVR's sub-processors are Anthropic (reads images, writes answers), OpenAI (turns generated text and your questions into search embeddings), and the backend is hosted on Railway with data stored in Google Firebase.
  • What is kept. The original file is deleted once processing completes. BEHAVR keeps the generated description, the extracted text and, where available, a small thumbnail. There is currently no delete endpoint. To request deletion of your data, email support@behavr.in.
  • Ids and questions. Your client id and agent id are sent with each upload, and the questions you send to ask are sent to BEHAVR.
  • BEHAVR does not sell your data.

Questions about your data: support@behavr.in.

Troubleshooting

  • The server shows as "failed" in Claude Code or Cursor. Check BEHAVR_API_KEY first. If it is not set, the server does not start and writes BEHAVR_API_KEY is not set to stderr.
  • Error 401. The API key is missing or invalid.
  • Error 403. Your key is fine, but your plan limit has been reached (monthly image or video limit) or your subscription has expired. Don't regenerate the key; check your plan.
  • `remember` times out. Processing may still be running. Don't upload the file again right away; call ask about it after a minute.
  • "Only image/video files can be remembered". Only jpg, jpeg, png, heic, webp, mp4, mov, avi, mkv and webm files are accepted. The path must also be absolute; a relative path is rejected with "file_path must be an absolute path".
  • Video uploads fail. Video requires a paid BEHAVR plan.

Known limits

  • The allowlist checks the file extension only, not the file content.
  • The end-to-end script uploads one image per run, and there is currently no delete endpoint, so that memory stays under its mcp-e2e- client.

Development

npm test      # builds, then runs unit tests with a fake client (no network)

The end-to-end check talks to the real BEHAVR backend. It starts two server instances with the same BEHAVR_CLIENT_ID=mcp-e2e- and different agent ids, remembers an image on one and asks about it from the other. It reads its key only from BEHAVR_E2E_API_KEY and stops if that is not set; it never uses BEHAVR_API_KEY or a .env file.

$env:BEHAVR_E2E_API_KEY = "your-test-key"

$env:BEHAVR_E2E_IMAGE = "C:\path\to\screenshot-with-text.png" npm run e2e

BEHAVR_E2E_QUESTION optionally overrides the question. Each run leaves its memories in BEHAVR under its own mcp-e2e- client id.

License

MIT

Ask PopNx