Academic MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOSI_API_KEY | No | Individual API key for the LOSI (National Assembly Library Legislative Information) provider. | |
| CINII_API_KEY | No | Individual API key for the CiNii (Japanese scholarly papers) provider. | |
| HISTORY_API_KEY | No | Individual API key for the HGIS (National Institute of Korean History) provider. | |
| ENABLED_PROVIDERS | No | Comma-separated list of academic databases to enable. Example: kci,oak,kostma,losi,cinii. Default providers include kci, oak, and kostma. | kci,oak,kostma |
| DATA_GO_KR_API_KEY | No | API key from the Public Data Portal (data.go.kr), required for NL (National Library), KoreanTK, and Eyis providers. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | 여러 학술 DB에서 논문/문헌을 통합 검색합니다. 키워드, 저자, 연도 등으로 검색할 수 있습니다. |
| get_paper_detailC | 논문/문헌의 상세 정보(초록, 키워드, 인용정보 등)를 조회합니다. |
| list_providersB | 사용 가능한 학술 DB 목록을 조회합니다. |
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 clearly distinct purpose with no ambiguity: get_paper_detail retrieves detailed metadata for a specific paper, list_providers shows available academic databases, and search performs cross-database searches. There is no overlap in functionality that would cause misselection.
All three tools follow a consistent verb_noun pattern (get_paper_detail, list_providers, search). While 'search' is a single verb without an explicit noun, it fits naturally as a search action in this context and maintains readability with the other tools.
With only 3 tools, the set feels thin for an academic research server. While the tools cover basic operations (search, detail retrieval, provider listing), more comprehensive functionality like citation analysis, paper recommendations, or database-specific operations would enhance the scope. It's borderline but functional for minimal use.
The tool surface covers core search and retrieval workflows but has notable gaps. There is no way to save papers, manage collections, track citations over time, or access full-text content. Agents can work around this by using the provided tools, but advanced academic tasks will be limited.