Sensei MCP
Sensei MCP is a specialized server offering expert guidance for Dojo and Cairo development on Starknet, focusing on the Dojo ECS (Entity Component System) framework.
Key capabilities:
Provide beginner introductions and high-level overviews via
dojo_101Assist with project configuration (dependencies, profiles, permissions) using
dojo_configGuide implementation of Dojo systems and game logic through
dojo_logicHelp create and manage Dojo models and data structures with
dojo_modelSupport test writing for Dojo applications using
dojo_testDetail token standard implementations (ERC20, ERC721, ERC1155) with
dojo_tokenOffer comprehensive guidance across all development aspects via
dojo_sensei
Technical expertise includes:
Cairo's unique language features (ownership, memory, types)
Dojo ECS architecture (Models, Systems, World patterns)
Best practices for Starknet smart contract and onchain game development
Recommended incremental development workflow
Provides a way to run the Sensei MCP directly from GitHub using npx, allowing developers to access specialized tools for Dojo and Cairo development without local installation.
Enables installation and execution of the Sensei MCP server through the npm package manager using npx commands.
Offers configuration guidance for Scarb.toml files in Dojo projects, helping developers properly set up dependencies and project settings.
Click on "Deploy 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., "@Sensei MCP help me create a Position model for my Dojo game"
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.
Sensei MCP
Sensei MCP is a Model Context Protocol (MCP) server that provides expert guidance for Dojo and Cairo development on Starknet. It serves as your personal Dojo Sensei, offering specialized knowledge and assistance for building onchain worlds using the Dojo Entity Component System (ECS) framework.
Features
Expert Cairo Guidance: Get help with Cairo's unique ownership, memory, and type systems
Dojo ECS Architecture: Learn about Models, Systems, and World patterns
Smart Contract Development: Best practices for Starknet smart contracts
Specialized Tools: Access topic-specific tools for models, systems, testing, and more
Related MCP server: Starknet MCP Server
Using with Cursor
Installation
See the official Cursor docs for more information on installing and using MCP servers.
To add Sensei to your Cursor IDE:
Open Cursor command palette (⌘+Shift+P)
Type in "Cursor Settings" to open up the settings menu
Navigate to "MCP Tools" and click "New MCP Server"
Add the following configuration to
mcp.json:
{
"mcpServers": {
"sensei": {
"type": "command",
"command": "npx github:dojoengine/sensei-mcp",
"enabled": true
}
}
}Save the file
Cursor will attempt to initialise the server. Once initialised, the menu should look like this:
Note: you may need to install the server manually by running
npx github:dojoengine/sensei-mcpin your terminal before Cursor will pick it up.
Use
Once installed, Cursor Agent will automatically query Sensei when appropriate. Follow these best practices for optimal results:
Always mention the specialized tools: Explicitly ask the agent to use Sensei's specialized tools (e.g., "Please use the dojo_model tool to help me create a model").
Follow the incremental development approach:
Start with project setup using
dojo_101Define models first using
dojo_modelImplement systems next using
dojo_logicConfigure the project last using
dojo_configAdd tests using
dojo_test
Be specific in your requests: For example, instead of asking "Help me with my Dojo game," say "Please use the dojo_model tool to help me create a Position model for my game."
Break down complex tasks: Ask for help with one component at a time rather than requesting an entire game implementation at once.
Example prompt:
I'm building a Dojo game. First, please use the dojo_101 tool to help me set up the project structure.
After that, I'll need help creating the models using the dojo_model tool.Using with Claude Code
To add Sensei MCP to Claude Code, run the following command:
claude mcp add sensei-mcp npx github:dojoengine/sensei-mcpRunning Directly
You can also run Sensei MCP directly in the terminal:
npx github:dojoengine/sensei-mcpAvailable Tools
Sensei provides specialized tools for different aspects of Dojo development:
dojo_101: Beginner-friendly introduction to Dojo development
dojo_config: Essential guidance for configuring Dojo projects
dojo_logic: Expert guidance on implementing Dojo systems and game logic
dojo_model: Specialized guidance for creating and working with Dojo models
dojo_test: Comprehensive guide for writing tests for Dojo applications
dojo_token: Detailed guidance on implementing token standards in Dojo
How to Use Tools
When chatting with Sensei, you can ask for specific guidance by mentioning the tool name:
Can you help me understand how to create a model in Dojo?Sensei will automatically use the appropriate tool (in this case, dojo_model) to provide specialized guidance.
Recommended Development Workflow
For the best results, follow this incremental development approach:
Project Setup (use
dojo_101)Initialize your project with
sozo initUnderstand the project structure
Remove or replace boilerplate code
Define Models (use
dojo_model)Create your game state models
Ensure proper trait derivation
Set up key fields correctly
Implement Systems (use
dojo_logic)Create system contracts
Implement game mechanics
Handle state changes
Project Configuration (use
dojo_config)Set up Scarb.toml
Configure Dojo profiles
Manage dependencies
Testing (use
dojo_test)Write comprehensive tests
Verify game logic
This workflow ensures you build your Dojo application in a structured, methodical way, leveraging the specialized knowledge of each tool at the appropriate stage of development.
Core Expertise
Sensei has deep expertise in:
Cairo programming language (including its unique ownership, memory, and type system)
Dojo ECS architecture (Models, Systems, and World)
Smart contract development on Starknet
Best practices for onchain game development
Development
Project Structure
bin/: Contains the executable scriptsrc/: Source code for the MCP serverprompts/: Text prompts for different aspects of Dojo developmentresources/: Additional resources used by the prompts
Building from Source
# Clone the repository
git clone https://github.com/dojoengine/sensei-mcp.git
cd sensei-mcp
# Install dependencies
npm install
# Build the project
npm run build
# Start the server
npm startAvailable Tools
7 toolsdojo_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.
Inputs: no named parameters.
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.
Inputs: no named parameters.
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.
Inputs: no named parameters.
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.
Inputs: no named parameters.
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.
Inputs: no named parameters.
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.
Inputs: no named parameters.
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
The OpenZeppelin Cairo Contracts MCP server generates secure smart contracts in the Cairo language for Starknet environments based on OpenZeppelin templates. It brings OpenZeppelin's proven security and style rules directly into AI-driven development workflows to create safe, production-ready contracts. Key capabilities include providing templates for ERC-20, ERC-721, ERC-1155, Multisig, Governor, and Vesting contracts.
A Model Context Protocol server for Wix AI tools
The OpenZeppelin Solidity Contracts MCP server integrates OpenZeppelin's security and style rules into AI-driven development workflows, enabling AI assistants to generate safe, correct, and production-ready smart contracts. It automatically validates generated code against OpenZeppelin standards (including imports, modifiers, naming conventions, and security checks) and supports various contract types including ERC-20, ERC-721, ERC-1155, Stablecoins, RWA, Governor, and Account contracts through prompt-driven workflows.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server enabling AI assistants to create, buy, and sell tokens on the Pump.fun platform on Solana.621ISC
- AlicenseBqualityDmaintenanceA comprehensive Model Context Protocol server that enables AI agents to interact with Starknet blockchain, query data, manage wallets, and work with smart contracts.2535 npm7MIT

CodeAlive MCPofficial
AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.90MIT- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI agents to Dune Analytics data, providing access to DEX metrics, EigenLayer statistics, and Solana token balances through structured tools.2MIT