CiNii MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CINII_APP_ID | Yes | Your CiNii API Application ID. |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| advanced_search_detailedC | CiNiiで高度な検索を行い、論文情報を取得する |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear from its name and description.
The single tool uses a descriptive snake_case name that aligns with common MCP naming conventions. With only one tool, there are no inconsistencies to evaluate.
One tool is on the low end and feels thin for a server named CiNii, which typically implies a richer API surface. However, the tool itself is comprehensive enough to perform advanced searches, so it's borderline.
The server only offers a single search tool. It lacks dedicated operations for fetching paper details by ID, managing result pagination, or accessing related resources like authors or references, leaving significant gaps for a full CiNii integration.