nightglass MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| take_screenshotA | Take a screenshot of a website. Returns the screenshot as a PNG image. Supports viewport screenshots, full-page captures, and mockup mode (screenshot wrapped in a browser frame). |
| check_balanceA | Check your nightglass account balance and remaining screenshot credits. |
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 2 tools
The two tools have completely distinct purposes: take_screenshot handles capturing website screenshots, while check_balance manages account credits. There is no overlap or ambiguity between them.
Both tools follow the consistent verb_noun pattern: take_screenshot and check_balance. The naming is clear, predictable, and matches the action they perform.
With only two tools, the server feels thin for a screenshot service. A typical screenshot API might include additional tools for managing captures, listing history, or configuring settings, but the current count is borderline acceptable.
The server covers the core screenshot-taking workflow and account balance check. Minor gaps exist (e.g., no history, download, or retry options), but the primary use case is fully addressed.