Jij MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| learn_jijmodelingC | |
| jm_checkC | |
| qiskit_v0tov1v2_migration_guideB | |
| qiskit_v1_api_reference_tocA | |
| qiskit_v2_api_reference_tocB | |
| qiskit_tutorialA | |
| qiskit_code_static_checkA | |
| fetch_as_markdownA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| jijmodeling://docs/guide | |
| jij://quantum/qiskit/v1v2migration-guide |
TDQS
Scored across 8 tools
Most tools have distinct purposes, with clear separation between JijModeling and Qiskit domains. However, there is some potential confusion between 'qiskit_v0tov1v2_migration_guide' and 'learn_jijmodeling' as both are educational guides, and 'qiskit_v1_api_reference_toc' and 'qiskit_v2_api_reference_toc' are very similar in function. The descriptions help clarify, but the boundaries could be slightly ambiguous.
The naming is mixed with no consistent pattern. Some tools use snake_case (e.g., 'fetch_as_markdown', 'jm_check'), while others use descriptive phrases with underscores (e.g., 'qiskit_v0tov1v2_migration_guide'). There is no uniform verb_noun structure, and names vary in length and style, making them less predictable.
With 8 tools, the count is reasonable for a server covering JijModeling and Qiskit support. It's slightly on the higher side but manageable, as each tool serves a specific function without obvious redundancy. The scope is well-defined, though it could be streamlined.
For the JijModeling domain, there is a check tool and a learning guide, but no creation or execution tools, leaving gaps. For Qiskit, there are checking, tutorial, migration, and API reference tools, which cover educational and reference needs but lack direct code execution or quantum computing operations. The surface is functional but incomplete for full workflow support.