theminjoo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to run the server on. Provided by deployment platforms; defaults to 8000. | 8000 |
| THEMINJOO_BASE_URL | No | Base URL of the source news listing. Default: https://theminjoo.kr/main/sub/news | https://theminjoo.kr/main/sub/news |
| THEMINJOO_MCP_TOKEN | No | Optional bearer token protecting the /mcp endpoint. If unset, /mcp is unauthenticated. | |
| THEMINJOO_CORS_ORIGINS | No | Comma-separated allowed CORS origins. Default: * | * |
| THEMINJOO_MAX_PAGE_SIZE | No | Maximum allowed page size. Default: 100 | 100 |
| THEMINJOO_REQUEST_TIMEOUT | No | Timeout in seconds for upstream requests. Default: 15 | 15 |
| THEMINJOO_CACHE_TTL_SECONDS | No | Cache TTL in seconds. Default: 300 | 300 |
| THEMINJOO_DEFAULT_PAGE_SIZE | No | Default page size for list results. Default: 20 | 20 |
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_postsB | List official 더불어민주당 posts. board: 11=논평·브리핑, 230=모두발언. |
| get_postB | Get one official post including body text and metadata. |
| search_postsB | Search recent post titles across up to 10 list pages. |
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 role: list_posts returns posts from a specific board, get_post retrieves a single full post, and search_posts finds posts by title across recent pages. There is no meaningful overlap that would confuse an agent.
All tool names follow the same verb_noun pattern (list_posts, get_post, search_posts) with consistent snake_case. The naming is predictable and standard.
Three tools is slightly minimal but appropriate for a read-only content retrieval server focused on official party posts. Each tool serves a distinct retrieval need without redundancy.
For a read-only posting board domain, list/get/search covers the essential lifecycle of content discovery and retrieval. Minor additions like category filtering or pagination details could be nice, but the core surface is sufficient and has no dead ends.