peoplesoft
Related Servers
Alternatives to peoplesoft
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides direct SQL access to a locally hosted Reactome database, enabling schema discovery, guarded read-only queries, and ergonomic helpers over the full relational schema.9MIT
- FlicenseAqualityDmaintenanceProvides read-only access to a local MySQL database, enabling SQL queries, database and table listings, and table schema descriptions.4-
- AlicenseAqualityCmaintenanceExecute SQL queries, browse schemas, and analyze Oracle Database performance through an AI-compatible Model Context Protocol server.84MIT
- FlicenseAqualityCmaintenanceEnables read-only access to a SQLite shop database through domain entity tools and pre-built analytic answers, without exposing raw SQL.9-
- FlicenseAqualityBmaintenanceEnables LLMs to answer small business finance questions about spending, sales trends, cash flow projections, and profitability using a local SQLite database.6-
- AlicenseAqualityDmaintenanceProvides read-only MySQL query execution, database/table browsing, and table structure inspection with SQL safety validation.56 npmMIT
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: describe_table/list_tables are schema introspection, query_peoplesoft_db is raw SQL, and the rest are semantic domain queries. However, check_project_billing_setup overlaps somewhat with get_project_contracts and list_contracts in coverage of the project/contract/bill-plan relationship, and the schema-inspection tools (describe_table, list_tables) somewhat duplicate what the semantic tools already encapsulate.
Naming follows a mostly consistent verb_noun pattern: describe_table, list_tables, list_projects, list_contracts, get_project_contracts, get_bill_plan. Minor deviations exist such as query_peoplesoft_db, check_project_billing_setup, and the verbose cost_reimbursable_billable_transactions, which break the tight verb_noun convention but are still readable and descriptive.
9 tools is within the well-scoped 3-15 range. The count is reasonable for a PeopleSoft contracts/billing domain, though there is some redundancy—the low-level SQL/schema tools (describe_table, list_tables, query_peoplesoft_db) plus the four semantic getters make the surface feel slightly overlapping rather than lean.
The read-side surface is well covered: projects, contract lines, bill plans, billing setup diagnostics, and billable transaction summaries are all represented. However, the server is entirely read-only—there are no create/update/delete operations for any resource, which is acceptable for a query/data-analysis server but means lifecycle coverage is intentionally partial rather than complete.