nascoder-terminal-browser-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| terminal_browseA | Browse websites and display content directly in terminal without saving files. Supports multiple terminal browsers (lynx, w3m, links) with fallback to fetch+html-to-text. |
| check_browsersA | Check which terminal browsers are available on the system |
| extract_linksA | Extract all links from a webpage without displaying the full content |
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
Each tool has a clear, distinct purpose: browsing, checking available browsers, and extracting links. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (terminal_browse, check_browsers, extract_links), making the set predictable and easy to navigate.
With only 3 tools, the server is tightly scoped to terminal browsing. Each tool is essential and there is no bloat or redundancy.
The tool surface fully covers the stated domain: browsing content, checking browser availability, and extracting links. There are no obvious gaps for typical terminal browsing workflows.