bcquality-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BCQUALITY_LAYERS | No | Enabled layers, in order of increasing precedence. | microsoft,community,custom |
| BCQUALITY_REPO_URL | No | URL used for auto-clone and refresh. | https://github.com/microsoft/BCQuality.git |
| BCQUALITY_REPO_PATH | No | Local path to a clone of BCQuality. If set, overrides cache. | |
| BCQUALITY_AUTO_CLONE | No | If false and no clone exists, error at startup. | true |
| BCQUALITY_CACHE_PATH | No | Directory where the server clones if no REPO_PATH is provided. | %LOCALAPPDATA%\bcquality\cache (Windows) / ~/.cache/bcquality (Unix) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bcquality_list_domainsA | Lists all knowledge domains (performance, security, privacy, …) present in the configured BCQuality clone, with file counts and which layers contribute. |
| bcquality_list_knowledgeB | Lists knowledge files with optional filters on layer, domain, technologies, bc-version, countries, application-area, and keywords. Supports pagination via limit/offset. |
| bcquality_list_skillsA | Lists all skills (meta-skills under /skills/, host-skill adapters at skills//SKILL.md, and action skills under /skills/). Filter by layer or kind (action-skill | host-skill | meta). |
| bcquality_get_knowledgeA | Returns the parsed frontmatter, title, and named sections (Description, Best Practice, Anti Pattern, …) of a knowledge file, plus the paths of associated .good.al / .bad.al examples if present. |
| bcquality_get_examplesA | Returns the content of the .good.al and/or .bad.al example files sibling to a knowledge file. |
| bcquality_get_skillA | Returns the parsed contents of a skill file — either a meta-skill (skills/entry.md, read.md, do.md, write.md) or an action skill under /skills/. |
| bcquality_search_knowledgeA | Free-text search over knowledge files. Tokenizes the query and scores against frontmatter keywords, title, domain, and the Description section. Combine with structured filters for narrow results. |
| bcquality_get_applicable_for_contextA | Workflow tool — given a development goal and a BC context (technologies, bc-version, …), returns all knowledge files that match every frontmatter dimension, with sections inlined for direct LLM consumption. Applies layer precedence: custom > community > microsoft. Suppressed candidates are surfaced for transparency. |
| bcquality_statusA | Returns the active clone path, its source (env/cache/cloned), the current commit, the actual origin remote of that clone alongside the configured repo URL, the enabled layers, article counts per layer, and the in-memory index age. |
| bcquality_refreshA | Runs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: list/get/search for knowledge, list/get for skills, list domains, get examples, status, refresh, and context-aware retrieval. Even the three knowledge-discovery tools (list, search, applicable-for-context) are differentiated by filtering, free-text scoring, and layer-precedence workflow.
Most tools follow a consistent bcquality_<verb>_<noun> pattern (get_knowledge, list_skills, search_knowledge). Two names deviate slightly: bcquality_status is noun-only and bcquality_get_applicable_for_context uses a longer phrasal object, but the pattern remains predictable.
Ten tools is a well-scoped size for a knowledge/retrieval server. Each tool covers a distinct retrieval or maintenance operation without redundancy or feature creep.
The surface covers discovery (list domains/knowledge/skills), retrieval (get_knowledge/get_skill/get_examples/get_applicable_for_context), search, and maintenance (status/refresh). This is complete for a read-only knowledge MCP; no obvious dead ends remain.