Databases
rossdata.dev
Provides schema exploration and metadata lookup for the Ross ERP 8 database.
ENDPOINT 1
https://mcp.rossdata.dev/mcp
MCP server metadata
- Name
- rossdata.dev
- Version
- 1.0.0
Reference for the standard Ross ERP 8.0 database schema (FIN + MAN). It describes the shape of the database, not its contents: table and column definitions, DDL, the UI menu tree and the program catalog. No business data, no customer records, no program source — structure only. SCHEMA layer: start with schema_stats to orient, list_objects to browse/filter by type or module, find_column to locate a column across tables. Use lookup_table for a full object, search_columns to find objects/columns, get_ddl for CREATE TABLE, and graph_neighbors / path_between to explore how objects connect. Not sure which layer a term lives in? search_all spans schema, facilities and programs in one call. APPLICATION layer: the client menu tree of UI facilities (screens / reports / inquiries / maintenance functions). Use facility_stats to orient, list_facilities / search_facilities to find a screen, lookup_facility for a facility's program, help, the tables it touches, and the facilities it invokes / is invoked by, table_facilities for the reverse — which screens read or write a given table — and facility_programs for the code that implements a screen. PROGRAM CATALOG: the application source programs (metadata only, no source body). Use program_stats to orient, list_programs / search_programs to find a program, lookup_program for a program's type, procedures and the Data Dictionary tables it references, table_programs for the reverse — which programs reference a given table — and program_facilities for the screens a program backs. Object names and facility codes are upper-case, e.g. GL_ACCOUNTS, AP_A_002; program basenames are lower-case, e.g. ap_a_check_register.
Known tools 21
search_allCross-domain search in one call — spans schema objects, columns, UI facilities and programs at once.
Inferred read-onlygraph_neighborsList the knowledge-graph neighbours of an object — the programs, tables, views and procedures directly connected to it, with relationship type and direction.
Inferred read-onlytable_facilitiesReverse lookup: which UI facilities (screens/reports/programs) touch a given Ross ERP 8.
Inferred read-onlyfacility_programsCross-link a UI facility to the program(s) that implement it — 'what code runs this screen?
Inferred read-onlyprogram_facilitiesReverse of facility_programs: which UI facilities (menu screens / reports / inquiries) a program backs — 'what screens does this program run?
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.rossdata-dev]
url = "https://mcp.rossdata.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"rossdata-dev": {
"type": "http",
"url": "https://mcp.rossdata.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: rossdata-dev
Remote MCP URL: https://mcp.rossdata.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"rossdata-dev": {
"url": "https://mcp.rossdata.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"rossdata-dev": {
"type": "http",
"url": "https://mcp.rossdata.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "rossdata-dev",
"transport": "streamable-http",
"url": "https://mcp.rossdata.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for rossdata.dev was fetched 2026-08-23T19:29:10.921Z.
rossdata.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.