jaringan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| browser | No | Path to jaringan-browser binary | jaringan-browser |
| jrg-host | No | JRG TCP server hostname | localhost |
| jrg-port | No | JRG TCP server port | 7070 |
| file-root | No | Read from local .jrg files instead of TCP | |
| tcp-timeout | No | TCP connection timeout in ms | 5000 |
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jrg_fetchA | Fetch a Jaringan (JRG) page and return structured content (title, body, tags, links). Uses TCP to a JRG server by default, or a local file root. URL can be jrg://host:port/path or just a path like "welcome" or "/port-map". |
| jrg_fetch_rawA | Fetch a JRG page and return the raw protocol response (status line, headers, body). |
| jrg_inspectA | Inspect a JRG page and return a JSON manifest of interactive elements (headings, links, paragraphs, inputs, buttons). |
| jrg_searchA | Search local .jrg pages under a root directory. Returns matching page paths with snippets. |
| jrg_auth_listA | List all stored Jaringan authentication tokens. |
| jrg_viewB | Render a JRG page as formatted plain text (human-readable). |
| jrg_listA | List all available Jaringan pages. Returns an array of { slug, title } entries. |
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 7 tools
Each tool has a distinct purpose: listing tokens, fetching pages in different formats (structured, raw, plain text), inspecting interactive elements, listing all pages, and searching local pages. The fetch variants are clearly differentiated by their output format, leaving no ambiguity.
All tools follow a consistent 'jrg_verb' pattern with verbs like list, fetch, inspect, search, view. The compound 'auth_list' and 'fetch_raw' still adhere to the imperative style, making the naming predictable and easy to parse.
With 7 tools, the server covers the core reading operations (list, fetch, inspect, search) without being excessive or sparse. The count feels well-scoped for a focused Jaringan page retrieval and discovery surface.
The tool set is read-only, providing listing, fetching, inspecting, and searching, but lacks any write operations such as create, update, or delete pages. While it may suffice for read-only use cases, it is incomplete for a general-purpose Jaringan server that would typically include content management.