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-docsB | 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 | Refresh the cached AL-Go documentation 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-discussionsB | Search for relevant discussions in the AL-Go repository |
| alg-get-scenariosB | Get available AL-Go setup scenarios |
| alg-search-issuesC | Search for tips and tricks in resolved AL-Go issues |
| 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 knowledge sources or entire cache |
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
There is significant overlap among specialist-related tools (search, list, get, ask, get-knowledge) and search tools (discussions, issues, docs, semantic). Descriptions help differentiate but agents may still struggle to choose correctly.
All tools use 'alg-' prefix followed by verb_noun pattern. Slight inconsistency with compound verbs like 'build-knowledge-graph' and 'graph-visualization', but overall consistent.
17 tools is on the higher side but justifiable given the multiple knowledge sources and specialist features. Not excessive.
Covers specialists, discussions, issues, docs, workflows, and cache management. Semantic search bridges sources. Minor gap: no direct tool to execute or trigger workflows.