bc-source-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BC_SOURCE_REPO_URL | No | URL du repo upstream -- override si vous avez un fork | StefanMaron/MSDyn365BC.Sandbox.Code.History |
| BC_SOURCE_CACHE_DIR | No | Cache local (partial clone + worktrees + SQLite). ~2-5 Go selon les versions indexees. | ~/.bc-source-mcp/ |
| BC_SOURCE_LOG_LEVEL | No | trace/debug/info/warn/error/fatal | info |
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 |
|---|---|
| bc_list_branchesA | Lists all branches available in the upstream BC sources repository (Stefan Maron mirror). Each branch corresponds to a (localization, version) pair, e.g. "w1-26", "fr-27-vNext". By default, meta/internal branches (main, base, core, serena) are filtered out. Set include_meta=true to include them. |
| bc_list_versionsA | Lists the Business Central major versions for which sources are available in this MCP. Set include_vnext=true to also list the preview/-vNext variants. |
| bc_list_localizationsA | Lists the country/region codes available as branches in the upstream repository, with their human-readable names. "w1" is the worldwide base. |
| bc_find_object_across_branchesA | Searches for an AL object (by type and exact name) across all branches that have already been indexed in this MCP instance. Use this to compare presence/path of an object across versions or localizations. Does not trigger indexing — call bc_list_apps on a branch first if you want to include it. |
| bc_list_appsA | Lists top-level application folders in a given branch (e.g. "Base Application", "System Application", "Business Foundation"). If the branch has not been indexed yet, this triggers a first-time fetch + sparse-checkout + indexing (can take 1-5 minutes the first time). |
| bc_list_objectsA | Lists AL objects in a branch, with optional filters by type, app, and name pattern. Use "*" as wildcard in name_pattern (translated to SQL LIKE %). Triggers indexing on first use of a branch. |
| bc_get_objectA | Returns the AL source of a specific object (table, page, codeunit, report, enum, query, xmlport, or any extension). Identifies the object by branch + type + name (case-insensitive on type, exact on name). Triggers indexing on first use of a branch. Use line_start/line_end to fetch only a slice (1-indexed, inclusive) — useful for large objects (~100k lines). Use include_source=false to skip the source and get only metadata (size, total_lines). |
| bc_get_event_publishersA | Lists all event publishers ([IntegrationEvent], [BusinessEvent], [InternalEvent]) defined inside a specific AL object. Returns the event name, kind, full procedure signature, attribute, and source line. Useful for finding events to subscribe to. |
| bc_get_procedureA | Returns the signature, body, attributes, and modifier of a named procedure within an AL object. Useful when you only need a single procedure rather than the full object source. |
| bc_search_codeA | Searches AL source code in a branch using regular expressions (ripgrep). Returns matching lines with optional context. Filter by object_type (file suffix, e.g. "table" → "*.Table.al") or by app (top-level folder). Triggers indexing on first use of a branch (for the worktree). |
| bc_search_ftsA | Token-based full-text search across indexed AL sources using SQLite FTS5. Faster than bc_search_code (no disk re-scan) and supports cross-branch queries. Use FTS5 syntax: bare terms ("Customer Posting"), phrases (""Sales Header""), boolean (term1 AND term2), prefixes (Cust*). Returns ranked snippets with matched tokens wrapped in <<...>>. For regex patterns, prefer bc_search_code. |
| bc_refreshA | Re-fetches a branch from upstream and re-indexes it. If branch is omitted, refreshes every already-indexed branch sequentially. |
| bc_cache_statusA | Reports the total disk usage of the bc-source-mcp cache, the number of indexed branches, their object counts, and last fetch/index dates. |
| bc_prune_cacheA | Removes worktrees and index entries for branches not matching the keep filters. Pass keep_branches (explicit allowlist) or keep_versions/keep_localizations to retain only certain version/loc combinations. The partial-clone Git repo itself is never deleted. |
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 14 tools
Each tool has a clearly distinct purpose. bc_search_code (regex) and bc_search_fts (token-based) are differentiated, as are bc_find_object_across_branches (cross-branch) and bc_list_objects (single-branch listing). No overlapping or ambiguous tools.
All tools use the consistent prefix 'bc_', followed by a verb like list, get, search, find, prune, refresh. The pattern is uniform (verb_noun or verb_preposition_noun), with bc_cache_status being the only slight deviation but still clear.
14 tools is well-scoped for the domain of Business Central source code management. Each tool addresses a specific need (listing, searching, fetching, cache management) without unnecessary redundancy or overload.
The tool surface covers read-only operations comprehensively: listing branches/versions/localizations/objects/apps, fetching source and procedures, searching, and cache management. A minor gap is lack of a direct diff tool between branches, but the core workflow is fully supported.