Skip to main content
Glama
Sign In
peoplesoft

peoplesoft

by Jcurrin27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to peoplesoft

No user-submitted related servers found.

    Related Servers

    • local-mysql

      myexperimenthub
      F
      license
      A
      quality
      D
      maintenance
      Provides read-only access to a local MySQL database, enabling SQL queries, database and table listings, and table schema descriptions.
      4
      -

    • legacy-db-mcp

      0103juan
      A
      license
      A
      quality
      C
      maintenance
      Lets an LLM explore a cryptic legacy ERP schema in plain language through a semantic layer (table listing, column descriptions, published dictionary) and run single read-only SELECT queries that return capped results. Enforces safety at the database engine level: only reads are authorized, sensitive columns are masked to NULL, queries are aborted after a few seconds, and every call is written to an append-only audit log.
      3
      MIT

    • finanzas-pyme

      JuanDsm04
      F
      license
      A
      quality
      B
      maintenance
      Enables LLMs to answer small business finance questions about spending, sales trends, cash flow projections, and profitability using a local SQLite database.
      6
      -

    • knowledge-base

      sigpima
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and compare paint-contracting quotations and estimates, explaining price differences by materials, labor, or profit, summarizing projects, searching work items, and running read-only SQL against the Postgres data.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    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 Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources