Ross ERP Data Dictionary is an MCP server with 21 tools an agent can call, among them facility_programs, facility_stats, find_column. It answers at https://mcp.rossdata.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Structure-only reference for the vanilla Ross ERP 8.0 schema, UI menu tree, and program catalog.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
facility_programs | Cross-link a UI facility to the program(s) that implement it — 'what code runs this screen?'. Each program carries a match label: declared (named by the facility's menu entry, authoritative) or titleId (TITLE id equals the facility code). C Inputs: code |
facility_stats | Overview of the Ross ERP 8.0 application layer — the client menu tree of UI facilities (screens, reports, inquiries, maintenance functions): total facilities, and their breakdown by system (e.g. ACCOUNTS_PAYABLE), database (FIN/MAN) and cla |
find_column | Look up a single column by exact name across the whole Ross ERP 8.0 schema: its description, valid values, notes, every table that carries it, and any foreign-key roles it plays. Inputs: name |
get_ddl | Return the CREATE TABLE (DDL) for a Ross ERP 8.0 table, with column descriptions as comments plus primary-key and foreign-key constraints. Inputs: name |
graph_neighbors | List the knowledge-graph neighbours of an object — the programs, tables, views and procedures directly connected to it, with relationship type and direction. Inputs: name, limit |
list_facilities | Browse and filter Ross ERP 8.0 UI facilities (menu screens/functions). Filter by system, database, class, a name/code substring, or withTables (only facilities whose table cluster is known); paginate with limit/offset. Returns summaries — u Inputs: system, database, class, q, withTables, limit |
list_objects | Browse and filter Ross ERP 8.0 objects (tables / views / procedures / functions). Filter by type, database, module, or a name substring; paginate with limit/offset. Returns object summaries — use lookup_table for full detail. Inputs: type, db, module, q, limit, offset |
list_programs | Browse and filter Ross ERP 8.0 programs (application source, metadata only). Filter by module (ap, gl, ic, sop, ...), type (a=archive, i=inquiry, m=maintenance, r=report, s=server, l=load, u=utility, ...), layer (base | vendor-core), titled Inputs: module, type, layer, titled, q, limit |
lookup_facility | Full detail for one Ross ERP 8.0 UI facility by code: its name, system, database, class, GEMBASE program, help text, menu paths, the physical table cluster it touches — core (the working set the screen is built on) and reference (control/lo Inputs: code |
lookup_program | Full detail for one Ross ERP 8.0 program, by TITLE program-id (e.g. AP_A_002) or source basename (e.g. ap_a_check_register): its module, type, layer, declared title, internal PROCEDURE_FORM procedures, the Data Dictionary tables it referenc Inputs: id |
lookup_table | Full schema for a Ross ERP 8.0 object (table / view / procedure / function): columns with type, nullability, keys, descriptions and valid values, foreign keys in and out, related tables, and usage. Inputs: name |
path_between | Find the shortest path between two objects in the Ross ERP 8.0 knowledge graph (how A reaches B through calls / references / accesses). Inputs: from, to |
program_facilities | Reverse of facility_programs: which UI facilities (menu screens / reports / inquiries) a program backs — 'what screens does this program run?'. One program often serves several facilities. Lookup by TITLE id (e.g. AP_I_001) or basename (e.g Inputs: id |
program_stats | Overview of the Ross ERP 8.0 program catalog — every application-source program (metadata only, no source body): total programs, how many declare a TITLE id, how many carry Data Dictionary table links, total program→table edges, read/write |
schema_stats | Overview of the Ross ERP 8.0 schema in one call: object counts by type, module list, total/distinct columns, audit-twin pairs, and the top tables/columns/modules. Use this first to orient before drilling in. |
search_all | Cross-domain search in one call — spans schema objects, columns, UI facilities and programs at once. Use this when you don't yet know which layer a term lives in (e.g. 'check register' is a screen, a program and a table). Scope to one layer Inputs: query, type, limit |
search_columns | Search the Ross ERP 8.0 schema by name (and column descriptions). Returns matching objects and columns. Inputs: query, limit |
search_facilities | Search Ross ERP 8.0 UI facilities by code, name, help text, program or tag. Use this to find the screen/report for a task, e.g. 'check register' or 'purchase order receipts'. Inputs: query, limit |
search_programs | Search Ross ERP 8.0 programs by basename, TITLE program-id, title, module or type. Use this to find the program behind a task, e.g. 'check register' or 'ap_a'. Inputs: query, limit |
table_facilities | Reverse lookup: which UI facilities (screens/reports/programs) touch a given Ross ERP 8.0 table — split into core (facilities whose working set includes it) and reference (facilities that use it as a control/lookup), each with how many time Inputs: table |
table_programs | Reverse lookup: which standard Ross ERP 8.0 programs reference a given table (validated against the Data Dictionary). Answers 'what code touches this table?' — complements table_facilities (which answers 'what screens touch it?'). Metadata Inputs: table |
Every block below points at https://mcp.rossdata.dev/mcp. Pick your client and copy.
claude mcp add --transport http ross-erp-data-dictionary https://mcp.rossdata.dev/mcp
{
"mcpServers": {
"ross-erp-data-dictionary": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.rossdata.dev/mcp"]
}
}
}{
"mcpServers": {
"ross-erp-data-dictionary": {
"url": "https://mcp.rossdata.dev/mcp"
}
}
}{
"servers": {
"ross-erp-data-dictionary": {
"type": "http",
"url": "https://mcp.rossdata.dev/mcp"
}
}
}{
"context_servers": {
"ross-erp-data-dictionary": {
"url": "https://mcp.rossdata.dev/mcp"
}
}
}{
"mcpServers": {
"ross-erp-data-dictionary": {
"serverUrl": "https://mcp.rossdata.dev/mcp"
}
}
}{
"mcpServers": {
"ross-erp-data-dictionary": {
"url": "https://mcp.rossdata.dev/mcp"
}
}
}name: Ross ERP Data Dictionary
version: 0.0.1
schema: v1
mcpServers:
- name: Ross ERP Data Dictionary
type: streamable-http
url: https://mcp.rossdata.dev/mcp{
"mcpServers": {
"ross-erp-data-dictionary": {
"httpUrl": "https://mcp.rossdata.dev/mcp"
}
}
}{
"mcpServers": {
"ross-erp-data-dictionary": {
"type": "http",
"url": "https://mcp.rossdata.dev/mcp"
}
}
}{
"mcpServers": {
"ross-erp-data-dictionary": {
"url": "https://mcp.rossdata.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.rossdata.dev%2Fmcp&type=streamable_http&id=ross-erp-data-dictionary&name=Ross%20ERP%20Data%20Dictionary
It answered our last check on 19 October 2026 in 188 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by rossdata.dev and served from mcp.rossdata.dev, the vendor's own domain: https://mcp.rossdata.dev/mcp.
21, as returned by the server's own tools/list on 11 September 2026: facility_programs, facility_stats, find_column, get_ddl, graph_neighbors, list_facilities, list_objects, list_programs, and 13 more.
It answered our last check on 19 October 2026 in 188 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.rossdata.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.rossdata. Endpoint host: mcp.rossdata.dev. ARD identifier: urn:air:dev.rossdata:mcp:data-dictionary.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.