Sw Dev Knowledge Base MCP

Name: Sw Dev Knowledge Base MCP
Author: execuro

by execuroversion 0.1.7i★ –iRuns on your computer

Registry nameio.github.execuro/sw-dev-knowledge-base-mcp

Install

Overview

Description from the maker (original English)

Read-only offline MCP server over a curated Shopware developer knowledge base

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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: Search & AI memory

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).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "sw-dev-knowledge-base": {
      "command": "npx",
      "args": [
        "-y",
        "@execuro-sw-ecosystem/sw-dev-knowledge-base-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add sw-dev-knowledge-base -- npx -y @execuro-sw-ecosystem/sw-dev-knowledge-base-mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "sw-dev-knowledge-base": {
      "command": "npx",
      "args": [
        "-y",
        "@execuro-sw-ecosystem/sw-dev-knowledge-base-mcp"
      ]
    }
  }
}

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": {
    "sw-dev-knowledge-base": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@execuro-sw-ecosystem/sw-dev-knowledge-base-mcp"
      ]
    }
  }
}

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.

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account execuro, 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 Search & AI memoryi

More stars than 0% of the other 7226 servers in this category
Published to the registry more recently than 71% of the other 7226 servers in this category
Basic checks equal to or better than 100% of the other 7226 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 Sw Dev Knowledge Base 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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.7) reached the registry 15 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: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 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.

sw-dev-knowledge-base-mcp

A read-only, offline MCP server that lets a coding agent ls/grep/cat a curated Shopware developer and merchant knowledge base without leaving its session — plus the factory that builds that knowledge base.

The corpus ships inside the package, so the server needs no network at runtime, no API key and no index: it is a filesystem view over plain Markdown.

Install

npx -y @execuro-sw-ecosystem/sw-dev-knowledge-base-mcp@<version>

Node >= 20. The published package declares no dependencies — its two third-party libraries, @modelcontextprotocol/sdk and zod, are inlined into dist/server.js, and every other import is a node: builtin. Their licences are in THIRD-PARTY-NOTICES.md.

Configure it as an MCP server

"mcpServers": { "ShopwareDevKnowledgeBase": { "command": "npx", "args": ["-y", "@execuro-sw-ecosystem/sw-dev-knowledge-base-mcp@ "] } } }

Pin an exact version: the corpus is part of the package, so the version is the content.

Options, all optional:

Flag	Environment variable	Effect
`--wiki-root`	`WIKI_ROOT`	Serve an arbitrary wiki root instead of the packaged `wiki/`
`--corpus`	`KB_CORPUS`	Select a corpus defined in `kb.config.json` (the package ships only `wiki`)
`--project-wiki`	`KB_PROJECT_WIKI`	Add your own project wiki as a `project` layer; `off` disables it

The tools it exposes

Tool	Shell equivalent	What it returns
`list_docs`	`ls` (with `depth`, `glob`)	Directory entries, titles from frontmatter, the directory's `index.md`
`grep_docs`	`grep -rin` over `*.md`	Match lines with context, or `files`/`count` modes
`read_doc`	`cat` / `sed -n`	A page or line range, its frontmatter and a citable `path:from-to`
`kb_status`	`cat /manifest.json`	Which layers and corpus are served, with provenance and counts

Line numbers are identical to the shell's, so a grep_docs hit pages straight into read_doc. There is no ranking and no search engine: discovery quality comes from the corpus's own index.md lines, keywords, hubs and synonyms file. The server writes nothing and opens no network connection.

What is in the corpus

wiki/platform/ — a retrieval-oriented rewrite of Shopware's official documentation: developer docs for 6.6 and 6.7, merchant/functional docs, topic hub pages, curated per-version guideline files and a synonyms index. It is path-addressed: version and doc type are directories (platform/dev/6.7/…, platform/func/…), never parameters. wiki/README.md describes the layout and how to navigate it with a plain shell.

The published tarball is 2.7 MB (10.0 MB unpacked, 2006 files); its top level is exactly LICENSE README.md THIRD-PARTY-NOTICES.md dist kb.config.json package.json wiki.

Working on this repository

End users never clone this repository — it is the *factory* that produces the package above:

Path	What it is
`src/`	MCP server source (builds `dist/server.js`)
`ingest/`	The deterministic ingest CLI: sync, pages, hubs, guidelines, build, synonyms, lint
`wiki/`	The generated documentation corpus — never hand-edited, except `wiki/platform/index.md`
`test/`	Server and ingest test suite (`node --test`): 465 tests, zero skips
`scripts/`	`setup-sources.mjs`, `setup-docs.mjs`, `pack.mjs`
`docs/`	Maintainer guides — see Documentation
`.claude/`	`kb-factory-` skills, pinned writer/verify agents, and the two `kb-verify-` hooks
`.sources/`	Gitignored, created by `npm run setup` — pinned Shopware source and docs clones

npm ci

npm run setup # fetches .sources/ — see "One-time setup" below npm run build # typecheck + bundle src/ -> dist/server.js npm test # build, then the full test suite npm run wiki:lint # blocking schema/link/id/size checks over wiki/platform/

Run /kb-factory-setup (a Claude Code skill, see CONTRIBUTING.md) once per clone before running the verify suite or an ingest writer — it installs the two hooks that keep each agent inside its own corpus, without which neither is trustworthy.

One-time setup — what `npm run setup` actually does

npm run setup fetches two things you did not ask for by name into a gitignored .sources/:

~250 MB of pinned Shopware source (.sources/shopware/ /, a sparse tag-pinned git checkout — not a composer install, no PHP needed) that the code check and code-evidence lanes read.
~1 GB of official documentation clones (.sources/docs/{developer,merchant}/) that the docs test corpus serves.

It is idempotent, resumable and an offline no-op once satisfied. The `merchant` documentation mirror is a private repository. On a host without access, setup prints what is unavailable and continues — that is deliberate: a missing optional input degrades the run rather than failing it, and the committed wiki/platform/func/ layer stays usable either way. Full detail: docs/sources.md.

Documentation

docs/producer-manual.md — building, code-checking, verifying and shipping the corpus; the full skill-driven ingest workflow.
docs/sources.md — what .sources/ holds and how npm run setup builds it.
docs/releasing.md — npm setup, tagging, publishing and post-publish verification.
CONTRIBUTING.md — toolchain, test/lint gates, CI's zero-skips rule.
CHANGELOG.md — Keep a Changelog format.
THIRD-PARTY-NOTICES.md — licences of the code inlined into dist/server.js.

Licence

MIT, Execuro UG (haftungsbeschränkt). See THIRD-PARTY-NOTICES.md for the licences of the third-party code inlined into dist/server.js.

Sw Dev Knowledge Base MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

sw-dev-knowledge-base-mcp

Install

Configure it as an MCP server

The tools it exposes

What is in the corpus

Working on this repository

One-time setup — what npm run setup actually does

Documentation

Licence

One-time setup — what `npm run setup` actually does