Cookbook Shelf MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EYB_DEMO | No | Set to 1 for the MCP server's fictional demonstration mode. | |
| EYB_HEADED | No | Set to 1 to show the MCP query browser. | |
| EYB_CDP_URL | No | Attach to a dedicated, already-running local Chrome window. | |
| EYB_PROFILE_DIR | No | Dedicated profile directory shared by login, CLI, and MCP. | |
| EYB_BROWSER_CHANNEL | No | Browser channel: chromium (default), chrome, or msedge. | chromium |
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 |
|---|---|
| list_cookbooksB | List cookbooks on the user's EYB shelf and known indexing coverage. Bounded, read-only. |
| search_my_recipesA | Find recipe references only in cookbooks on the user's shelf. Ingredient mode checks listed ingredient phrases; dish mode checks title/category candidates and can include served-with dishes. Search is limited to EYB's indexed keyword candidates. Always check truncation and missing metadata. |
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 cleanly separated purposes: one inventories the shelf and indexing coverage, the other searches recipe references within it. There is no functional overlap between them.
Both tools follow a snake_case verb_noun pattern: list_cookbooks and search_my_recipes. The 'my' qualifier in the second name is a minor modifier and does not break the overall convention.
With only two tools, the server feels minimally scoped and sits at the thin boundary for a useful MCP surface. It is reasonable for a narrow read-only use case but may leave agents wanting more.
The tools cover the core read-only workflow: listing shelf coverage and searching for recipe references by ingredient or dish. Richer recipe detail or shelf management functionality is likely out of scope, though it could be a minor gap in some workflows.