# How to use RevoGrid Pro MCP
URL: https://pro.rv-grid.com/guides/ai-mcp/
Source: src/content/docs/guides/ai-mcp.mdx
Description: Use the hosted RevoGrid MCP in Codex, Cursor, Claude Code, or VS Code to work with Pro docs, examples, plugins, migration notes, and typed API context.
RevoGrid Pro MCP gives AI coding tools structured access to RevoGrid knowledge through the hosted Pro endpoint:

```text
https://mcp.rv-grid.com/pro
```

When your client is configured with the Pro endpoint and a valid bearer token, agents can use Pro-only examples, advanced docs, richer feature resolution, and typed plugin context.

RevoGrid Pro has a wide plugin surface, richer examples, and advanced features like pivot, event manager, history, Pro renderers, and specialized editors. MCP helps an AI tool retrieve the right implementation guidance before it writes code.

## Your MCP token

If you are signed in to the RevoGrid Pro portal, use the token details below directly in your MCP client:

## What you can use it for

Use Pro MCP when you want an AI tool to:

- find the best Pro example for a specific framework
- determine whether a feature is public or Pro before suggesting code
- build around typed plugin APIs instead of guessing event names or option shapes
- gather migration notes before upgrading a Pro implementation
- work from real examples for pivot, export, filters, history, validation, or custom renderers

## Agent-readable documentation files

The portal also exposes Markdown text files for AI tools that do not use MCP directly:

- [`/llms.txt`](/llms.txt) — a concise index of the most useful RevoGrid Pro and Enterprise documentation links.
- [`/llms-full.txt`](/llms-full.txt) — a full normalized Markdown export of the portal documentation corpus.

Use MCP when your tool supports retrieval with authentication and typed context. Use the `llms.txt` files when your agent needs a public, text-only documentation source it can fetch directly.

## How to access Pro MCP

RevoGrid Pro users should connect to the dedicated Pro endpoint:

```text
https://mcp.rv-grid.com/pro
```

Pro access requires both:

- the Pro MCP URL: `https://mcp.rv-grid.com/pro`
- an `Authorization` header in the format `Bearer <your-mcp-token>`

### MCP token flow

RevoGrid Pro MCP works best when each Pro user receives their own MCP token.

High-level flow:

1. RevoGrid configures the MCP server with `MCP_AUTH_JWT_SECRET`.
2. The portal generates a signed JWT token for the signed-in Pro user.
3. The user connects their MCP client to `https://mcp.rv-grid.com/pro`.
4. The user sends that token in the request header as `Authorization: Bearer <token>`.
5. Valid token requests are treated as Pro and unlock Pro-only MCP results.

The user should receive a token, not the raw `MCP_AUTH_JWT_SECRET`. The secret stays on the MCP server and is only used to sign and verify tokens.

### Access checklist

1. Have an active RevoGrid Pro subscription or trial.
2. Sign in to the RevoGrid Pro portal.
3. Add `https://mcp.rv-grid.com/pro` to Codex, Cursor, Claude Code, or VS Code.
4. Copy your token from this page and configure your MCP client to send `Authorization: Bearer <your-token>`.
5. If the agent only sees public results, contact RevoGrid support and ask them to verify MCP access for your Pro account.

If you can connect to the MCP server but only receive public documentation or Core-only matches, your client is most likely connected successfully but not yet provisioned for Pro-aware retrieval.

## What Pro access changes

With Pro access enabled, the MCP can help the agent retrieve:

- Pro-only docs and examples
- advanced plugin guidance
- Core vs Pro feature resolution
- richer typed context for Pro plugins and workflows
- better matches for pivot, event manager, history, export, validation, and advanced filters

## Recommended setup

1. Add the Pro MCP endpoint to your AI coding tool.
2. Add your MCP token to the client as an authorization header in the format `Authorization: Bearer <your-mcp-token>`.
3. Ask the agent to search MCP before writing code.
4. Ask it to validate the final implementation against RevoGrid types and examples.

## Install in AI coding tools

### Claude Code

```bash
claude mcp add --transport http revogrid https://mcp.rv-grid.com/pro
```

Then configure the server to send:

```text
Authorization: Bearer <your-mcp-token>
```

### Codex

```bash
codex mcp add revogrid --url https://mcp.rv-grid.com/pro
```

Then configure the server to send:

```text
Authorization: Bearer <your-mcp-token>
```

### Cursor

```json
{
  "mcpServers": {
    "RevoGrid": {
      "url": "https://mcp.rv-grid.com/pro",
      "type": "http",
      "headers": {
        "Authorization": "Bearer <your-mcp-token>"
      }
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "RevoGrid MCP": {
      "url": "https://mcp.rv-grid.com/pro",
      "type": "http",
      "headers": {
        "Authorization": "Bearer <your-mcp-token>"
      }
    }
  },
  "inputs": []
}
```

## How to prompt effectively

The best prompts tell the agent three things:

1. your framework
2. whether the solution may use Pro features
3. which RevoGrid behavior matters most

### Good prompt examples

- `Build a Vue RevoGrid Pro pivot table. Search MCP first, use the best matching Pro example, and explain the required plugin configuration.`
- `Create a React grid with RevoGrid Pro history and validation. Use MCP docs and types before writing code.`
- `Find the best RevoGrid Pro example for advanced filter headers in Angular and adapt it to server-side filtering.`
- `Use RevoGrid Pro MCP to implement row master with nested editing. Validate the final API names against types.`
- `Check if this feature is available in Core or Pro, then recommend the best matching RevoGrid implementation path.`

## Best practices for Pro usage

Prompt the agent to inspect RevoGrid MCP before generating code. This reduces invented APIs and helps it start from real examples.

RevoGrid has strong typing. Ask the agent to verify plugin names, event payloads, config fields, and feature usage against RevoGrid types.

If your implementation is allowed to use Pro features, say so. If you need a Core-only fallback, ask for that explicitly.

Ask the agent to use the best matching Pro demo or guide as the starting point, then adapt it to your app.

## Typical Pro workflows

### Build advanced features faster

Use MCP when implementing:

- pivot tables
- history and undo flows
- advanced filters
- custom editors and renderers
- row master, row transpose, and row order
- validation, charts, and export

### Migrate more safely

Ask the agent to retrieve migration notes and typed API context before changing:

- plugin setup
- advanced grid config
- event handling
- framework wrapper integration

### Review existing code

Ask the agent to compare your local code with:

- the closest Pro example
- the relevant plugin docs
- the matching typed API symbols

## Example workflow

1. Add `https://mcp.rv-grid.com/pro` to your MCP client.
2. Open your RevoGrid Pro project.
3. Ask the agent to find the best matching Pro example and docs.
4. Ask it to adapt that result to your framework and data model.
5. Ask it to verify the result against RevoGrid types before finalizing.

## Suggested first prompts

- `Show me the best RevoGrid Pro examples for pivot in React.`
- `Find the Pro docs and type context for event manager.`
- `Use RevoGrid Pro MCP to build advanced filter headers in Vue.`
- `Review this implementation and compare it to the nearest RevoGrid Pro example.`

## Related pages

- [Welcome to the RevoGrid Pro documentation!](/guides/)
- [Installing RevoGrid Pro](/guides/installation)
- [Pivot](/guides/data-manage/pivot)
- [Event Manager Explanation](/guides/data-manage/event-manager-explanation)
- [Features](/guides/faq/features)
