AL-Go MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token for higher rate limits and full API access to discussions and issues. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| alg-search-docsC | Search through AL-Go documentation for specific queries |
| alg-get-workflowsB | Get examples of AL-Go GitHub workflows |
| alg-get-server-versionA | Get version information for the AL-Go MCP server |
| alg-refresh-cacheB | Load the AL-Go documentation index (cached for 24 hours). Use force=true to re-download it from the repository. |
| alg-search-specialistsC | Search for AL-Go specialists by name, persona, expertise, or keyword |
| alg-list-specialistsA | List all available AL-Go specialists and their persona names. After browsing, use alg-ask with the specialist parameter to connect with a specific specialist. |
| alg-get-specialistB | Get detailed information about a specific AL-Go specialist |
| alg-askA | Consult an AL-Go domain specialist for expert guidance on AL-Go workflows, CI/CD pipelines, releases, testing, and Business Central app development. Auto-selects the best specialist based on your question, or use the specialist parameter to request a specific persona (e.g. 'freddy', 'casey', 'rex'). Use this whenever the user asks about AL-Go or addresses a specialist directly (e.g. '@alg-freddy ...', 'alg-freddy ...', 'ask riley about releases'). |
| alg-search-discussionsA | Search the 50 most recently active GitHub Discussions in the AL-Go repository. Requires a GitHub token. |
| alg-get-scenariosB | Get available AL-Go setup scenarios |
| alg-search-issuesA | Search the 100 most recently closed AL-Go issues for tips and workarounds |
| alg-get-specialist-knowledgeB | Get comprehensive knowledge for a specialist including workshops, scenarios, discussions, and issues |
| alg-build-knowledge-graphB | Initialize and build the knowledge graph linking specialists to all knowledge sources |
| alg-semantic-searchB | Intelligent cross-source search across workshops, scenarios, discussions, and issues using relevance scoring |
| alg-graph-visualizationC | Get knowledge graph structure for visualization (nodes and edges) |
| alg-cache-statsA | Get cache hit rates and statistics for knowledge sources |
| alg-clear-cacheB | Clear cached GitHub data so the next request re-downloads it. 'docs' covers documentation, scenarios and workshops. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| al-go-setup-help | Get help with setting up AL-Go for Business Central projects |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-version | Version information for the AL-Go MCP server |
| al-go-repo-info | Basic information about the AL-Go repository |
| al-go-doc | Get content from a specific AL-Go documentation file |
| specialists-list | List of all available AL-Go specialists |
| specialist-detail | Get details about a specific AL-Go specialist |
TDQS
Scored across 17 tools
Several tools overlap: alg-search-docs/discussions/issues all search single sources while alg-semantic-search searches across all of them, and the specialist cluster (search/list/get/get-knowledge/ask) has fuzzy boundaries between browsing, fetching, and consulting. The cache trio (refresh/clear/stats) is also easily conflated, though descriptions do provide reasonable guidance.
Nearly all tools use a consistent 'alg-' prefix with a verb_noun pattern (get-workflows, search-docs, list-specialists, clear-cache). A few deviate—alg-semantic-search, alg-graph-visualization, and alg-cache-stats are noun/adjective phrases rather than verb-led—but the overall pattern stays predictable.
17 tools is slightly heavy but justifiable given the server spans documentation search, specialist consultation, caching, and a knowledge graph. The count is on the upper edge of comfortable rather than excessive.
The surface covers search across docs/discussions/issues, specialist discovery and consultation, cache lifecycle, and knowledge-graph construction/visualization. Minor gaps exist (no direct scenario/workshop retrieval beyond knowledge aggregation), but core workflows appear well covered.