Skip to main content
Glama
Sensei MCP

Sensei MCP

by dojoengine

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:

  1. Open Cursor command palette (⌘+Shift+P)

  2. Type in "Cursor Settings" to open up the settings menu

  3. Navigate to "MCP Tools" and click "New MCP Server"

  4. Add the following configuration to mcp.json:

{
  "mcpServers": {
    "sensei": {
      "type": "command",
      "command": "npx github:dojoengine/sensei-mcp",
      "enabled": true
    }
  }
}
  1. 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-mcp in 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:

  1. 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").

  2. Follow the incremental development approach:

    • Start with project setup using dojo_101

    • Define models first using dojo_model

    • Implement systems next using dojo_logic

    • Configure the project last using dojo_config

    • Add tests using dojo_test

  3. 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."

  4. 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-mcp

Running Directly

You can also run Sensei MCP directly in the terminal:

npx github:dojoengine/sensei-mcp

Available 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.

For the best results, follow this incremental development approach:

  1. Project Setup (use dojo_101)

    • Initialize your project with sozo init

    • Understand the project structure

    • Remove or replace boilerplate code

  2. Define Models (use dojo_model)

    • Create your game state models

    • Ensure proper trait derivation

    • Set up key fields correctly

  3. Implement Systems (use dojo_logic)

    • Create system contracts

    • Implement game mechanics

    • Handle state changes

  4. Project Configuration (use dojo_config)

    • Set up Scarb.toml

    • Configure Dojo profiles

    • Manage dependencies

  5. 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 script

  • src/: Source code for the MCP server

  • prompts/: Text prompts for different aspects of Dojo development

  • resources/: 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 start

Available Tools

7 tools
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.

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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      90
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      2
      MIT