ExisJS

ExisJS MCP Server (@exisjs/mcp)

The Model Context Protocol (MCP) server allows AI coding assistants (such as Google Antigravity, Claude Code, Cursor, and Windsurf) to introspect your ExisJS project, query local framework documentation, and scaffold idiomatic boilerplate code.


Overview

When developing with ExisJS, external AI models may occasionally generate outdated patterns from other frameworks. The @exisjs/mcp server connects your AI assistant directly to your local project environment, ensuring:

  1. Version-Matched Offline Documentation: The AI queries documentation bundled directly with your project's installed @exisjs packages.
  2. Deterministic Scaffolding: The AI uses verified code generators for routes, boundaries, validation schemas, plugins, and configuration files across both Functional and OOP paradigms.

Installation & Setup

Automatic Installation (add-mcp)

You can install @exisjs/mcp across all detected local coding agents:

npx add-mcp @exisjs/mcp@latest -y

Manual Configuration

Add @exisjs/mcp to your IDE's MCP configuration settings (mcp.json or settings file):

mcp.json
{  "mcpServers": {    "exisjs-mcp": {      "command": "npx",      "args": ["-y", "@exisjs/mcp@latest"]    }  }}

Claude Code Setup

Run the following command in your terminal:

claude mcp add exisjs-mcp npx @exisjs/mcp@latest

Cursor Setup

  1. Open Cursor Settings (Cmd+, or Ctrl+,).
  2. Navigate to Features > MCP.
  3. Click + Add New MCP Server.
  4. Set Name to exisjs-mcp.
  5. Set Command to npx -y @exisjs/mcp@latest.

Available MCP Tools

Once initialized, the assistant gains access to the following toolset:

1. Documentation Tools

Tool NameParametersDescription
exis_list_local_docs{}Scans and lists all available ExisJS documentation topics installed locally in node_modules.
exis_read_local_docs{ topic: string }Reads the markdown content for a specific documentation topic.

2. Code Generation & Scaffolding Tools

Tool NameParametersDescription
exis_generate_route{ filePath: string, paradigm: "functional" | "oop" }Scaffolds an idiomatic route controller file (route.ts).
exis_generate_boundary{ filePath: string, paradigm: "functional" | "oop" }Scaffolds a directory boundary middleware file (boundary.ts).
exis_generate_schema{ filePath: string }Scaffolds a typed tex validation schema file (schema.ts).
exis_generate_plugin{ name: string, filePath?: string }Scaffolds an ExisJS plugin module definition.
exis_generate_config{}Scaffolds a baseline exis.config.ts configuration file.

Practical AI Workflows

Example 1: Querying Framework APIs

DEFAULT

User Prompt: "How does dependency injection work with circular references in ExisJS?"

AI Execution:

  1. Invokes exis_list_local_docs to find relevant documentation keys.
  2. Invokes exis_read_local_docs({ topic: "providers" }) to inspect forwardRef() and @Inject().
  3. Generates the exact solution matching the installed version.

Example 2: Scaffolding a Protected Route

DEFAULT

User Prompt: "Scaffold a functional route in src/http/admin/users/route.ts with a validation schema."

AI Execution:

  1. Invokes exis_generate_route({ filePath: "src/http/admin/users/route.ts", paradigm: "functional" }).
  2. Invokes exis_generate_schema({ filePath: "src/http/admin/users/schema.ts" }).
  3. Customizes the handlers to fit the user's business requirements.