nii-research-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CINII_APP_ID | Yes | Your NII application ID used for CiNii Research. | |
| KAKEN_APP_ID | Yes | Your NII application ID used for KAKEN. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_articlesC | Search CiNii Research for article metadata. Pass next_start to read the next page. |
| search_recordsC | Search CiNii Research across all records or restrict to the specified record kind. |
| get_recordA | Get selected CiNii Research metadata for a CRID returned by search. |
| search_projectsC | Search KAKEN research projects by keyword. Use next_start to read the next page. |
| search_researchersC | Search KAKEN researchers by name and optionally by institution. |
| get_projectA | Look up an exact KAKEN project or area number, optionally prefixed with JP. |
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 6 tools
Most tools are clearly separated by resource and action: get_project vs. search_projects, search_records vs. get_record, and search_researchers are distinct. The main overlap is search_articles versus search_records, since search_records can apparently search across all record kinds including articles, but the descriptions make the specialized role of search_articles reasonably clear.
All six tools follow a consistent verb_noun naming pattern in snake_case: get_project, search_articles, search_records, get_record, search_projects, search_researchers. The singular/plural distinction between get_record and search_records is natural and not confusing.
Six tools are well-scoped for a research metadata server covering CiNii and KAKEN lookup operations. Each tool has a clear place: search and get for projects/records, plus targeted searches for articles, projects, and researchers without excessive surface area.
The surface covers the core read-only research workflows: article/record search, record retrieval by CRID, project search and exact project lookup, and researcher search. Minor gaps remain, such as no dedicated get_researcher by ID and no article-specific get tool, but get_record likely covers retrieval by CRID and agents can work around the researcher gap.