netsuite-suiteanalytics-odbc-mcp
Related Servers
Alternatives to netsuite-suiteanalytics-odbc-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceMCP server that exposes read-only NetSuite tools for querying warehouse stock levels and order status, using mock data locally and a pluggable client interface.2-
- AlicenseNot gradedqualityDmaintenanceA Python MCP server that connects to any ODBC data source and exposes schema discovery + query tools. Read-only by default, write access available per-connection.2MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server providing access to NetSuite data through OAuth 2.0 with PKCE authentication. Works seamlessly with any MCP-compatible client including Claude Code, Cursor IDE, and Gemini CLI.235 npm20MIT
- FlicenseAqualityDmaintenanceLocal stdio MCP server for read-only Microsoft SQL Server access through Python and pyodbc, providing test connection, list tables, describe table, and query tools.4-
- AlicenseNot gradedqualityFmaintenanceRead-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.MIT
- FlicenseNot gradedqualityDmaintenanceA versatile MCP server that connects to multiple relational databases (MySQL, PostgreSQL, Oracle, SQL Server, SQLite) and enables secure read-only SQL query execution and metadata access.4-
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: running queries, listing metadata, describing table columns, and checking status. There is no overlap or ambiguity between them.
All tools share a consistent 'netsuite_' prefix, but the second part mixes verbs (query, describe) and nouns (tables, status). The pattern is predictable though not strictly verb_noun.
With only 4 tools, the set is tightly scoped to the server's purpose of running SuiteAnalytics ODBC queries and exploring metadata. Each tool is essential and the count feels appropriate.
The toolset covers the core lifecycle of working with an ODBC data source: querying data, discovering tables, inspecting schemas, and checking connection health. No obvious gaps exist for the intended use case.