Goal
Build an MCP server for RDataCore instead of adding LLM-specific logic into the application itself.
The server should connect to the existing RDataCore API via api_key and use the current permission model as-is.
Why
- no separate AI logic inside RDataCore
- no duplicated business logic
- the API stays the single integration surface
- desktop and IDE LLM clients can use RDataCore through a standard MCP setup
Target users
- developers who want less custom integration work so non-technical staff can operate data workflows through LLM clients
- technical or AI-driven management users who can install and use MCP in desktop or IDE tools
Scope
- add a small Rust crate that runs as an MCP server
- connect it to RDataCore only through the existing API
- authenticate with
api_key
- expose a first set of useful MCP tools for RDataCore operations
- build binaries for macOS, Linux, and Windows
- distribute it through an npm package in the usual MCP style
Non-goals
- no embedded LLM assistant in
r_data_core
- no permission bypass
- no separate domain logic outside the existing API
First capabilities
- inspect entity definitions
- read and search entities
- inspect workflows
- expose useful system or capability metadata
Write operations can follow later once the read-oriented path is stable.
Success criteria
- RDataCore remains free of separate LLM orchestration logic
- an MCP-compatible desktop or IDE client can connect to RDataCore
- permissions are enforced through the existing
api_key
- installation is simple on major operating systems
Goal
Build an MCP server for RDataCore instead of adding LLM-specific logic into the application itself.
The server should connect to the existing RDataCore API via
api_keyand use the current permission model as-is.Why
Target users
Scope
api_keyNon-goals
r_data_coreFirst capabilities
Write operations can follow later once the read-oriented path is stable.
Success criteria
api_key