Refine MCP Server

Model Context Protocol (MCP) server for exploring and understanding the Refine framework.

Features

This MCP server provides tools for AI assistants to:

• Explore Structure: Navigate the Refine codebase directory tree
• Read Files: Access source code files for analysis
• Search Files: Find files by name pattern
• Get Packages: List all packages in the Refine monorepo with metadata
• Read Core Files: Quickly access key implementation files by category (data providers, auth, routing, hooks)

Auto-Clone Feature

The server automatically clones the Refine repository on first run if it doesn't exist locally. No manual setup required!

Installation

Global Installation (Recommended)

npm install -g @abdokouta/refine-mcp

Local Installation

npm install @abdokouta/refine-mcp

Usage

With Kiro IDE

Add to your .kiro/settings/mcp.json:

{
  "mcpServers": {
    "refine": {
      "command": "npx",
      "args": ["-y", "@abdokouta/refine-mcp@latest"],
      "disabled": false,
      "autoApprove": [
        "explore_structure",
        "read_file",
        "search_files",
        "get_packages",
        "read_core_files"
      ]
    }
  }
}

With Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "refine": {
      "command": "npx",
      "args": ["-y", "@abdokouta/refine-mcp@latest"]
    }
  }
}

Available Tools

explore_structure

Explore the directory structure of the Refine repository.

Parameters:

• maxDepth (optional): Maximum depth to explore (default: 3)

read_file

Read the content of a specific file.

Parameters:

• path (required): Relative path from refine-source root

Example:

{
  "path": "packages/core/src/index.ts"
}

search_files

Search for files by name pattern.

Parameters:

• pattern (required): File name pattern to search for

Example:

{
  "pattern": "provider"
}

get_packages

Get information about all packages in the Refine monorepo.

Parameters: None

read_core_files

Read multiple core implementation files at once.

Parameters:

• category (required): One of "data-provider", "auth-provider", "router", "hooks", "core", or "all"

Example:

{
  "category": "data-provider"
}

Environment Variables

• REFINE_SOURCE_PATH: Custom path for the Refine repository (optional, defaults to auto-clone location)

Use Cases

Understanding Data Providers

"How do Refine data providers work? Show me the core implementation."

The MCP will read the data provider interface and example implementations.

Debugging Auth Issues

"I'm having issues with authentication in Refine. Can you show me how auth providers are structured?"

Learning Refine Hooks

"Show me how useList and useOne hooks work in Refine"

Repository

The server clones from: https://github.com/refinedev/refine

License

MIT

Author

Abdo Kouta