This guide helps you connect the Lovrabet runtime MCP to AI tools such as Cursor and Claude Code. Once the key is configured, you can query app data and run existing business capabilities in natural language.

TIP

The runtime MCP targets business data and the capabilities of running apps. If your goal is to create projects, analyze databases, or generate pages and menus, use the Rabetbase development suite instead of this MCP.

Prerequisites

Before you start, make sure:

• You have access to at least one Lovrabet app
• You have obtained a personal AccessKey from the Lovrabet user center (<ACCESS_KEY> below stands for it — never put a real key into documents or share it with others)
• Your AI tool supports remote MCP (Streamable HTTP recommended)

Choose the server URL

Environment	MCP URL
Production	https://runtime.lovrabet.com/api/mcp

Use the production URL by default. Switch to a daily-environment URL only when your team explicitly agrees on it.

Configure it in Cursor

Open Cursor's MCP config file:

• macOS / Linux: ~/.cursor/mcp.json
• Windows: %APPDATA%/Cursor/mcp.json

Add the following configuration and replace <ACCESS_KEY> with your own key:

{
  "mcpServers": {
    "lovrabet-runtime": {
      "url": "https://runtime.lovrabet.com/api/mcp",
      "headers": {
        "X-Lovrabet-AccessKey": "<ACCESS_KEY>"
      }
    }
  }
}

If your AccessKey can access multiple apps, pin the target app as well — an overly broad scope in each conversation invites ambiguity in the AI's interpretation:

{
  "mcpServers": {
    "lovrabet-runtime": {
      "url": "https://runtime.lovrabet.com/api/mcp",
      "headers": {
        "X-Lovrabet-AccessKey": "<ACCESS_KEY>",
        "X-Lovrabet-App-Code": "<APP_CODE>"
      }
    }
  }
}

After saving, restart Cursor, or re-enable lovrabet-runtime in the MCP panel.

Other IDEs / Agents have different configuration entry points, but the core is the same: fill in the MCP URL and send the X-Lovrabet-AccessKey request header. For copy-and-paste configurations per client, see <cite doc-id="BpXOw0Q9Ai1irHklYa9cSJRYnKe" file-type="wiki" title="各 Agent 客户端配置运行态 MCP" type="doc"></cite>.

Verify the connection

Send the following prompts in order. If you get real account and app information back — not a generic explanation — the connection works.

Confirm your identity

帮我确认当前 Lovrabet 运行态 MCP 是否已认证，并告诉我当前登录用户是谁。

List accessible apps

列出我当前 AccessKey 能访问的应用。

Pin the current app (skip if already pinned in the header)

把当前会话切换到「<应用名称>」，之后的查询都在这个应用里执行。

Run one read-only query

在当前应用里找一下和「客户」相关的数据集，并列出前几条记录的摘要。

Configuration checklist

• [ ] The MCP URL matches your environment

• [ ] The header is X-Lovrabet-AccessKey with the correct key

• [ ] For multi-app scenarios, X-Lovrabet-App-Code is pinned, or an app has been selected in the chat

• [ ] MCP has been restarted / re-enabled after the config change

• [ ] The verification chat returned a real user, app, or dataset — not empty talk

Troubleshooting

Unauthenticated or authentication failed

First check that the header name is exactly X-Lovrabet-AccessKey (mind the casing and hyphens), and whether the key has expired or been reset. Never pass the key as a URL query parameter.

Connected, but data queries complain about a missing app

When your key can access multiple apps, the MCP does not default to the first one. Add X-Lovrabet-App-Code to the configuration, or have the assistant list apps and switch first.

How this differs from the old dev-mode Dataset MCP

The old Dataset MCP focused on development-side metadata and local startup. The runtime MCP is a hosted service that uses an AccessKey to access live business data and capabilities directly. For new integrations, prefer the runtime MCP described in this guide.

For common operations, write confirmations, and caveats once connected, see <cite doc-id="Um3KwCKyEiB56YkGDn2cuCuTnOh" file-type="wiki" title="用运行态 MCP 查询与处理业务数据" type="doc"></cite>.