Sensei MCP
Server 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 |
|---|---|
| dojo_101A | Beginner-friendly introduction to Dojo development. Use this when starting a new Dojo project, understanding the basic workflow, or when you need a high-level overview of the Dojo development process and architecture. |
| dojo_configB | Essential guidance for configuring Dojo projects. Use this when setting up Scarb.toml, creating dojo profile files, configuring permissions, setting up namespaces, or managing external contracts and dependencies. |
| dojo_logicA | Expert guidance on implementing Dojo systems and game logic. Use this when writing contract functions, implementing game mechanics, handling state changes, or working with the World contract to read/write models. |
| dojo_modelA | Specialized guidance for creating and working with Dojo models. Use this when you need to define data structures, create model schemas, implement model traits, or understand model relationships and constraints. |
| dojo_senseiB | The main system prompt for Dojo development. Use this as the primary prompt when starting a conversation about Dojo or Cairo development, or when you need comprehensive guidance across all aspects of Dojo development. |
| dojo_testA | Comprehensive guide for writing tests for Dojo applications. Use this when creating unit tests, integration tests, setting up test environments, or verifying the correctness of your Dojo systems and models. |
| dojo_tokenA | Detailed guidance on implementing token standards in Dojo. Use this when creating ERC20, ERC721, or ERC1155 tokens, implementing token functionality, or integrating tokens with your Dojo game. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| 101 | Beginner-friendly introduction to Dojo development. Use this when starting a new Dojo project, understanding the basic workflow, or when you need a high-level overview of the Dojo development process and architecture. |
| config | Essential guidance for configuring Dojo projects. Use this when setting up Scarb.toml, creating dojo profile files, configuring permissions, setting up namespaces, or managing external contracts and dependencies. |
| logic | Expert guidance on implementing Dojo systems and game logic. Use this when writing contract functions, implementing game mechanics, handling state changes, or working with the World contract to read/write models. |
| model | Specialized guidance for creating and working with Dojo models. Use this when you need to define data structures, create model schemas, implement model traits, or understand model relationships and constraints. |
| sensei | The main system prompt for Dojo development. Use this as the primary prompt when starting a conversation about Dojo or Cairo development, or when you need comprehensive guidance across all aspects of Dojo development. |
| test | Comprehensive guide for writing tests for Dojo applications. Use this when creating unit tests, integration tests, setting up test environments, or verifying the correctness of your Dojo systems and models. |
| token | Detailed guidance on implementing token standards in Dojo. Use this when creating ERC20, ERC721, or ERC1155 tokens, implementing token functionality, or integrating tokens with your Dojo game. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource-101 | |
| resource-config | |
| resource-framework | |
| resource-logic | |
| resource-model | |
| resource-test | |
| resource-token | |
| resource-dojo-documentation |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose with no ambiguity, as each targets a specific aspect of Dojo development (e.g., introduction, configuration, logic, models, testing, tokens, and a main prompt). The descriptions clearly differentiate their scopes, such as dojo_101 for beginners versus dojo_logic for expert guidance, ensuring agents can easily select the right tool.
All tool names follow a consistent 'dojo_' prefix pattern with descriptive suffixes (e.g., dojo_config, dojo_logic, dojo_model), using snake_case uniformly. This predictable naming scheme makes it easy for agents to understand the domain and purpose at a glance, with no deviations in style or convention.
With 7 tools, the count is well-scoped for the server's purpose of Dojo development guidance, covering key areas like setup, logic, models, testing, and tokens without being overwhelming. Each tool earns its place by addressing a distinct need, making the set comprehensive yet manageable for agents.
The tool surface is nearly complete for Dojo development, covering essential aspects from beginner introduction to advanced logic, models, testing, and token standards. A minor gap exists in deployment or integration tools, but core workflows are well-covered, allowing agents to work around any missing operations effectively.