Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@exia-scenario-generator MCP Server explain quantum computing in the Kotonoha Sisters style"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This is an MCP server that creates scenario files for the exia novel game engine.
Generate a scenario in the "Kotonoha Sisters Commentary" format and display it in exia.
Generate a scenario in the form of a "Kotoha Sisters Commentary" for a given topic
Convert the generated scenario into JSON format for exia
Download exia from GitHub and set it up
Displaying the generated scenario in exia
Related MCP server: VOICEPEAK MCP Server
Node.js v20.x or higher
OpenAI API Key
Git
Clone or download the repository
git clone https://github.com/kokushin/exia-mcp.git
cd exia-mcpInstall required packages
npm installCompile TypeScript (please run this after making any changes)
npm run buildLaunch Claude Desktop
Open the settings screen and add the MCP server
{
"mcpServers": {
"exia-scenario-generator": {
"command": "npx",
"args": [
"-y",
"/path/to/exia-mcp", //（clone した exia-mcp のパスに置き換えてください）
"--openai-api-key=YOUR_API_KEY", //（OpenAI API キーに置き換えてください）
"--stdio"
]
}
}
}※Please replace YOUR_API_KEY with your actual OpenAI API key.
* If npx cannot be executed, specify the absolute path.例: /path/to/.volta/bin/npx
Used in Claude Desktop as follows:
Type "Explain quantum computers on exia"
The MCP server starts, generates a scenario, and starts exia.
The exia application (Electron) starts in a separate window and plays the scenario.
generateScenario : Generate a scenario from a topic
setupExia : Download and set up exia
saveScenario : Save the generated scenario
exiaVoiceroidExplain : Runs everything from scenario generation to exia startup (recommended)
The first time you run it, it will take some time to download and set up exia.
You will need to prepare your own character images and replace them manually.
The exia documentation is here
Use of the OpenAI API may incur fees
MIT
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0exiaVoiceroidExplain2 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falsegenerateScenario2 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falsesaveScenario2 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falsesetupExia1 field changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"exiaVoiceroidExplaingenerateScenariosaveScenariosetupExiaThe tools appear to target distinct steps in a scenario generation workflow (setup, generate, save, explain), but the lack of descriptions makes it impossible to verify if there's overlap or ambiguity in their purposes. Without descriptions, an agent might guess incorrectly about boundaries, especially between generateScenario and exiaVoiceroidExplain.
Naming is inconsistent: generateScenario and saveScenario use camelCase, while exiaVoiceroidExplain and setupExia mix camelCase with unclear verb styles (e.g., 'exiaVoiceroidExplain' is a compound noun-verb hybrid). There's no predictable pattern across all tools, making them harder to parse as a set.
With 4 tools, the count is reasonable for a scenario generator server, suggesting a focused scope. It's not too thin or heavy, though the lack of descriptions makes it hard to assess if more tools might be needed for completeness.
Inferring from tool names, the domain is scenario generation with Exia/Voiceroid integration. The surface covers setup, generation, saving, and explanation, but without descriptions, it's unclear if there are gaps (e.g., listing, editing, or deleting scenarios). The absence of descriptions severely limits the ability to assess coverage, suggesting potential dead ends.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Generate logos, social posts, app screenshots, comic panels & visual-novel assets from prompts.
Generate full stories, chapters, characters & cover art from a premise (planner-writer pipeline).
Narrated, captioned videos from a topic or script, editable scene by scene.
Turn a topic, URL, or document into a narrated, animated explainer video.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kokushin/exia-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
