GLU Web Development MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLU_SITE | No | Andere openbare Notion-site gebruiken (Use a different public Notion site). | GLU Web Development |
| GLU_WORKERS | No | Gelijktijdige requests naar Notion. Hoger is sneller, maar dan krijg je eerder een rate limit (Concurrent requests to Notion. Higher is faster, but you may hit a rate limit sooner). | 3 |
| GLU_SPACE_ID | No | Andere openbare Notion-site gebruiken (Use a different public Notion site). | GLU Web Development |
| GLU_CACHE_DIR | No | Map voor de cache. Standaard: %LOCALAPPDATA%\glu-webdev-mcp (Windows), ~/Library/Caches/glu-webdev-mcp (macOS) of ~/.cache/glu-webdev-mcp (Linux) (Directory for the cache). | |
| GLU_MAX_CHARS | No | Maximale lengte van één antwoord; langere pagina's worden opgedeeld (Maximum length of a single response; longer pages are split). | 12000 |
| GLU_ROOT_PAGE | No | Andere openbare Notion-site gebruiken (Use a different public Notion site). | GLU Web Development |
| GLU_CACHE_HOURS | No | Hoe lang pagina's in de cache geldig blijven (How long pages remain valid in the cache). | 12 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_assignmentsB | List GLU Web Development assignments per leerjaar, plus other top-level pages. Lines: 'periode type: naam @ref'. |
| readA | |
| searchB | Full-text search across all pages (assignments, subpages, databases). Returns pages with @ref, assignment and snippet. All words must match. |
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 3 tools
The three tools have mostly distinct purposes: list_assignments browses top-level pages, read fetches a specific page/URL, and search performs full-text queries. There is minor overlap because list_assignments and search both return page references, but the descriptions make their primary roles clear.
All names are lowercase and use snake_case where multiword, but the pattern is mixed: list_assignments is verb_noun, while read and search are bare verbs. It remains readable, but the convention is not fully predictable.
Three tools are concise and well-scoped for a read-only Notion content access server. The count is slightly minimal, but each tool earns its place and there is no evidence of bloat.
The surface covers the core read-only workflow: browsing assignments, reading pages/URLs, and searching across content. Minor gaps exist, such as dedicated subpage or database listing beyond search/read, but agents can work around them by following references.