ochi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCHI_HOME | No | Moves ochi's home folder from its default platform-specific location. | |
| OCHI_PORT | No | Chrome debugging port. | |
| OCHI_CHROME | No | Path to the Chrome/Chromium/Brave/Edge executable. | |
| OCHI_CONFIG | No | Path to the ochi.toml configuration file. | |
| OCHI_PROFILE | No | Chrome profile directory to use. | |
| DISCOGS_TOKEN | No | Discogs API token (optional, for the discogs_* API tools). | |
| OCHI_EXTRACTORS | No | Path to your extractors folder. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Read a web page through the user's own Chrome (started automatically if needed). A site-specific extractor (if one matches the URL) returns clean structured data; otherwise a generic extractor returns the readable text of the page. Use for sites that block normal fetching (Discogs marketplace, Reddit, news). Discogs marketplace URLs accept ochi_max= to keep only cheaper items. |
| lookA | Read the page the user is looking at right now in the ochi browser (the visible tab),
or tab number |
| showA | Open a page for the user in a new visible tab of the ochi browser and leave it open ("look what I found"). Use sparingly: only when they'd want to see it themselves. |
| tabsB | List open tabs in the ochi browser (index, title, url, which one is visible). |
| browser_startA | Start the ochi Chrome (separate profile) if it isn't running; report its version. |
| browser_statusA | Is the ochi Chrome running? (does not start it) |
| list_extractorsA | List the site extractors ochi knows, with their URL patterns. |
| snapshotA | Save the rendered HTML of a page into snapshots/ (to write or debug an extractor). |
| discogs_searchC | Search the Discogs database. type: release | master | artist | label. format e.g. Vinyl. |
| discogs_releaseC | Release details: labels, formats, styles, tracklist, master_id, lowest price (EUR), have/want. |
| discogs_master_versionsC | All pressings of a master release (filter by format). |
| discogs_listingC | One marketplace listing: price, shipping to the logged-in user, seller rating, comments. |
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 12 tools
The browser tools are mostly distinct: fetch (read a URL), look (read the current visible tab), and show (open a page) each target a different action, and browser_start vs browser_status are clearly separated. The one mild overlap is fetch vs look, both read pages, but the descriptions draw a clear line (fetch navigates/fetches, look does not navigate).
There is a consistent discogs_ prefix for the four Discogs tools and a browser_ prefix for start/status, but the remaining tools use bare single-word verbs (fetch, look, show, tabs, snapshot) and a lone list_extractors, so no single predictable verb_noun convention spans the set. It stays readable but mixes conventions.
Twelve tools is well-scoped for a browser-automation-plus-Discogs server, with each tool covering a distinct capability (fetching, viewing, tab management, lifecycle start/status, extractor inspection, and four Discogs lookups). No tool feels redundant or padded.
The surface covers the core browsing lifecycle (start, status, tabs, fetch, look, show, snapshot, extractors) and Discogs search/release/master/listing flows. Minor gaps exist (e.g., no close_tab or general navigation/back operation), but the primary workflows are covered.