MEK MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host address to bind the server | 127.0.0.1 |
| PORT | No | Port number for the server | 10000 |
| MCP_TRANSPORT | No | Transport protocol for MCP server (e.g., 'sse' for SSE mode) | stdio |
| MEK_PLAYWRIGHT_HEADLESS | No | Run Playwright in headless mode | true |
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 |
|---|---|
| mek_search_simpleA | Search MEK bibliographic metadata (simple search). All provided fields are combined with AND logic. Supports wildcards with *. At least one of creator, title, subject, or mek_id must be provided. Args: creator: Author, editor, or translator name (e.g. "Ady", "Petőfi"). title: Book title or part of title. subject: Theme, keyword, or topic. mek_id: MEK document ID number. page_size: Results per page (10, 50, or 100). page: Page number (1-based). |
| mek_search_fulltextA | Search inside MEK document full text (HTML and PDF). Args: query: Words or phrase to find in document bodies. Use quotes for exact phrases. broadtopic: Optional collection filter: "", "science", "technical", "social", "humanities", "reference", or the full Hungarian topic string. page_size: Results per page (10, 50, or 100). page: Page number (1-based). |
| mek_search_advancedA | Advanced MEK bibliographic search with up to 5 field-specific criteria rows. Each row is a field + query pair. Rows are combined with AND/OR/NOT operators (operator between rows 1-2, operator2 between 2-3, etc.). MEK returns all hits in one list; max_results only limits how many documents are returned. Args: query: Search term for row 1. field: Row 1 field alias or raw MEK value (see mek_list_search_fields). field2: Optional row 2 field. query2: Optional row 2 search term. field3, query3: Optional row 3. field4, query4: Optional row 4. field5, query5: Optional row 5. operator: Combine rows 1 and 2: "and", "or", or "not". operator2: Combine rows 2 and 3. operator3: Combine rows 3 and 4. operator4: Combine rows 4 and 5. sort_by: Sort results by "title", "author", "date", or "id". accent_insensitive: Search without Hungarian accents when True. include_processing: Include in-processing documents when True. max_results: Maximum documents returned (MEK has no server-side paging). |
| mek_list_search_fieldsA | List available field names for mek_search_advanced and fulltext topic filters. |
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 4 tools
Each tool has a clearly distinct purpose: listing search fields, advanced multi-field search, fulltext search, and simple search. There is no overlap in functionality.
All tools follow a consistent snake_case pattern with the 'mek_' prefix and verb+modifier structure (list, search_advanced, search_fulltext, search_simple), making it predictable.
With 4 tools, the set is slightly on the lower end but well-scoped for a search-focused server. Each tool is essential, and the count does not feel excessive or insufficient.
The tool set covers multiple search modes and field listing, but lacks a direct tool to retrieve a specific document by ID or list all documents, which are notable gaps for a bibliographic library server.