Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

scree

de jrapakkoversión 0.4.1i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.jrapakko/scree

Instalar

Resumen

Descripción del creador (original en inglés)

Local semantic and keyword search over the markdown in a repo or notes folder.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Documentos, hojas de cálculo y oficina
  • Debes completar: OPENROUTER_API_KEY

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Descargar el archivo .mcpb del creador

El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.

Ejecuta esto en tu terminal

claude mcp add scree --env OPENROUTER_API_KEY=your-value -- docker run -i --rm -e OPENROUTER_API_KEY ghcr.io/jrapakko/scree:0.4.1 serve -notes /notes

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "scree": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1",
        "serve",
        "-notes",
        "/notes"
      ],
      "env": {
        "OPENROUTER_API_KEY": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "scree": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1",
        "serve",
        "-notes",
        "/notes"
      ],
      "env": {
        "OPENROUTER_API_KEY": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • OPENROUTER_API_KEY secreto obligatorio env
    OpenRouter API key, used to embed the notes when indexing and each query when searching.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub jrapakko, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Documentos, hojas de cálculo y oficinai

  • Más estrellas que el 0% de los otros 2180 servidores de esta categoría
  • Publicado en el registro más recientemente que el 89% de los otros 2180 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 2180 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro scree?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: OPENROUTER_API_KEY

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.4.1) llegó al registro anteayer.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker, MCPB en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Agent-Native Google Calendar - manage events, sync, and public booking

Se ejecuta en la nube★ 7620MITActualizado hace 2 meses
Instalar

Excel MCP Server

de haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

Se ejecuta en tu computadora★ 4276MITActualizado hace 6 días
Instalar

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Se ejecuta en tu computadora★ 847MITActualizado hace 3 días
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

scree

Local semantic search over the markdown in your repos and notes, served to Claude Code over MCP.

Scree splits markdown by heading, embeds the pieces through an API, and stores them in a SQLite file on disk, one index per folder. Claude Code asks for the few chunks that match a question instead of loading whole files. Each hit says which lines it came from, so Claude can read just those. The markdown stays the source of truth; an index can be deleted and rebuilt at any time.

See docs/SPEC.md for the design.

Quick start

You need Go 1.26 and an OpenRouter API key from https://openrouter.ai/settings/keys. The commands run from the root of this repo unless a step says otherwise.

  1. Build a static binary (no CGO):
   CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o bin/scree ./cmd/scree
  1. Save the key in the settings file. scree key prompts for it without echoing it, so it never lands in your shell history or on screen, writes ~/.config/scree/env with mode 600, and makes one test call to the API:
   bin/scree key

It keeps any other lines in the file and replaces an earlier key. scree key < file reads the key from the first line of a file instead, and replaces a saved key only with -replace; -offline skips the test call, and -check makes only the test call. Ctrl-C at the prompt saves nothing. To see Claude Code's OpenRouter costs apart from your own searches, save a second key with bin/scree key -mcp: scree mcp then uses it, and everything else keeps the first (settings file).

  1. Install the binary:
   mkdir -p ~/.local/bin

install -m 755 bin/scree ~/.local/bin/

Claude Code must find scree on its PATH. If ~/.local/bin isn't on it, add it in your shell profile.

  1. Check a repo before indexing it. scree run loads the settings file and runs a scree command. From inside the repo:
   cd ~/code/myrepo

scree run doctor -v

doctor -v lists every file that will be ignored and estimates the cost of indexing the rest. Add a .screeignore or .gitignore entry before indexing if anything private shows up as indexable.

  1. Turn scree on for the repo. From the repo's root:
   claude mcp add scree --scope project -- scree mcp

This writes .mcp.json with "command": "scree", "args": ["mcp"], with no key and no paths, so commit it. Claude Code asks each person to approve a project server once. Every session in the repo then keeps the index current; the first session builds it in the background. serve refuses a repo whose own .mcp.json doesn't name scree mcp, so a repo without this entry is never indexed, even if scree is also registered elsewhere. Don't register scree at user scope anyway.

Approving a project server means trusting the repo. Claude Code applies the env of a repo's .mcp.json, including PATH, before it starts the server, so a repo you approve decides which program scree is, and that program gets your settings file. Approve scree only in repos whose .mcp.json you trust, as you would any project server. To take that choice back for yourself, see absolute paths.

  1. Optional: a notes folder outside any repo. See A notes folder.

Build

Requires Go 1.26. No CGO. Tagged releases also publish prebuilt binaries for Linux, macOS and Windows (amd64 and arm64) on the GitHub releases page, a ghcr.io/jrapakko/scree image, and a Claude Desktop bundle, which scripts/mcpb.sh zips from the release's binaries.

CGO_ENABLED=0 go build -trimpath -ldflags='-s -w' -o bin/scree ./cmd/scree

Configure

Settings come from environment variables. The settings file is the one place to keep them, including the API key. Don't export the key in a shell profile. With OPENROUTER_API_KEY unset, a command run directly (scree search, doctor, reindex, watch) still uses the key in the settings file, by running as scree run would; see below.

VariableDefault
SCREE_DB$XDG_DATA_HOME/scree/indexes/ - /index.db, one per folder (or -db)
SCREE_MODELopenai/text-embedding-3-small
SCREE_DIMENSIONS512; 0 uses the model's default size
SCREE_EMBED_URLhttps://openrouter.ai/api/v1/embeddings
SCREE_MAX_FILE_BYTES1048576; larger files are skipped
SCREE_FIRST_SYNC_MB50; a Claude Code session or watch won't start the first index of a folder with more markdown than this (0 = no limit); scree reindex always does
SCREE_ZDR1; set 0 for endpoints other than OpenRouter
SCREE_HTTP_TOKENnone; required with serve -allow-remote, and enforced on loopback if set
SCREE_PAGERless -FRX from /usr/local/bin, /usr/bin or /bin; the pager for scree search's text view on a terminal, run without a shell: an absolute path or a name in those folders (never looked up on PATH), then its arguments. Set it empty for none
SCREE_COLORSword=1:match=1;33:link=36:lineno=2; the text view's colours as SGR codes (digits and ; only) for the word headings, the matched words, the locations and the line numbers. match= turns one off
OPENROUTER_API_KEYnone; when unset and the settings file holds one (scree key writes it there), search, reindex, doctor and watch run as scree run would. Without a key (unset or empty), notes are indexed for keyword search only and auto search runs keyword
SCREE_MCP_API_KEYnone; read only from the settings file (scree key -mcp writes it), and only by scree mcp, which passes it to serve as OPENROUTER_API_KEY instead of the file's own. Commands run directly and scree run never use it

$XDG_DATA_HOME defaults to ~/.local/share; a relative value is ignored. With neither it nor an absolute home directory, scree refuses to open an index unless -db names one.

Which folder. -notes names it on the command line. Without it, CLI commands use the git root of the current directory, or the current directory outside git. Under Claude Code, serve indexes the git root of the working directory Claude Code starts it in (the project, or the active worktree), refuses -notes, -db and SCREE_DB, and requires CLAUDE_PROJECT_DIR to be in the same repo; a .mcp.json can set environment variables but not the working directory. It also refuses a folder whose root .mcp.json names no scree mcp server. Outside Claude Code, serve has no default folder: pass -notes. A folder found automatically is refused if it is your home directory (from the password database, falling back to $HOME only if that lookup fails), a folder above it, or a filesystem root; on the command line, pass -notes to index it anyway. serve refuses such a folder even as -notes (a client such as Claude Desktop passes the folder a user picked) unless -allow-home is given. The check compares the folders themselves, not just their paths, so another path to your home folder (a bind mount, different letter case on macOS, /System/Volumes/Data/Users/…) is refused too. It only compares the chosen folder with your home folder and the folders above it, so a folder that holds a mount of your home somewhere inside it (as some containers and devcontainers set up) is not caught. Each index records its folder and refuses to be used for another one.

Changing the model or dimensions requires scree reindex -all. The index records which model built it and refuses to mix them.

Privacy

Every embedding request asks OpenRouter to route only to endpoints with zero data retention and data_collection: deny. A model with no such endpoint fails with a clear error naming the model, rather than falling back to one that keeps data. SCREE_ZDR=0 turns this off, which other OpenAI-compatible endpoints may need. Only chunk text, with its path and heading, is sent to the API; keyword search runs locally.

Ignoring files

An ignored file is never read for indexing, never sent to the embedding API, never returned by search, and refused by read_doc and reindex. Four layers decide:

  • Built-in: hidden files and folders, except the root .claude/ (not .claude/worktrees/), .github/, .gitlab/, .gitea/, .forgejo/, .cursor/, .codex/, .gemini/, .windsurf/, .circleci/ and .buildkite/; anything that isn't .md, .markdown or .mdc; symlinks that lead outside the folder; files over SCREE_MAX_FILE_BYTES; non-regular files such as FIFOs, which are never opened and which doctor reports as unreadable; and names with control characters.
  • `.gitignore`: in a git repo, everything git ignores (nested .gitignore files, .git/info/exclude, your global excludes file). Ignored folders such as node_modules/ are never read, and nested repositories are skipped. A tracked file that matches a pattern is still ignored. -gitignore=false turns this layer off.
  • `.screeignore` at the root of the indexed folder, in gitignore syntax.
  • Front matter: scree: ignore in a file's front matter.
# .screeignore

journal/ **/private-*.md /inbox/scratch.md !journal/public.md

include-hidden .name/ in .screeignore indexes another root hidden folder, and a pattern like /.cursor/ drops one of the defaults. A ! rule re-includes files inside an excluded folder, but never a file that a rule matched by name, so *.private.md stays ignored even under !archive/2024/; doctor -v lists what ! re-included. If .screeignore can't be read, is a symlink, or has a line scree can't parse, nothing is indexed until it is fixed; doctor names the bad lines by number.

---

scree: ignore


Run scree doctor -v to see what each layer ignores before relying on a pattern. The full rules are in docs/SPEC.md.

Use

scree key                # save the API key in the settings file

scree key -mcp # optional: a separate key for scree mcp (Claude Code) scree doctor # check config, index, and the API scree doctor -v # also list every ignored file, and check the keyword index scree reindex # index new and changed files scree reindex docs/a.md # re-index one file scree reindex -all # rebuild from scratch scree search "how do I rotate the backup keys" scree search -mode keyword PURGE_OLD_RECORDS # exact words, no API call scree search -format text "ci seed" # hits grouped by query word (the default on a terminal) scree search -no-pager "ci seed" # the same, printed without the pager scree search -format json "…" # one JSON object per hit scree search -format grep "…" # path:line:text, for fzf or vim -q scree watch # keep the index current (run as a service) scree serve -notes . # MCP over stdio, from a terminal scree serve -notes . -http 127.0.0.1:7077 # MCP over HTTP, loopback only scree indexes # list per-folder indexes; -prune deletes ones whose folder is gone

Every command but indexes and key takes -notes , -db and -gitignore=false. serve needs -notes outside Claude Code. From a terminal, search, reindex, doctor and watch run as scree run would whenever OPENROUTER_API_KEY is unset and the settings file holds a key; scree run loads the file in any case, for example scree run search "…".

Search modes

scree search -mode and the search_docs tool's mode take:

  • `auto` (the default): semantic, unless the query has an identifier-like word, a word with a letter plus _ or a digit, such as PURGE_OLD_RECORDS, psycopg_pool, R7-Q2 or v2, or a word from the folder's

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx