Skip to main content
Glama
HamishLacmane

nocodb-mcp-connector

Related Servers

Alternatives to nocodb-mcp-connector

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides full MCP integration with a self-hosted NocoDB instance, enabling LLMs to create, update, and delete bases, tables, fields, views, and records via 25 MCP tools.
      57 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Remote MCP server that auto-generates tools from NocoBase OpenAPI specs to enable full CRUD operations on collections across multiple instances. Supports streamable HTTP transport and API key authentication for secure, natural language interaction with NocoBase deployments.
      -
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with NocoBase instances for managing collections, UI schemas, flow models, and running API operations. It provides both hand-crafted tools and dynamically generated tools from NocoBase's OpenAPI specification.
      23
      5 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides tools for programmatically managing Airtable bases, tables, fields, and records through Claude Desktop or other MCP clients.
      12
      311 npm
      75
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A dual-transport MCP server that exposes your API as tools to LLM clients, supporting both stdio transport for local clients like Claude Desktop and HTTP/SSE transport for remote clients like OpenAI's Responses API.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for managing n8n workflows, allowing Claude and other MCP-compatible tools to create, read, update, delete, and execute workflows in your n8n instance.
      87 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. list_bases vs list_workspaces are clearly separated by workspace vs base, and descriptions clarify usage. list_records vs get_record differ in list vs single retrieval.

    Naming Consistency5/5

    All tools use verb_noun snake_case (list_bases, create_records, link_records, etc.) with no mixed conventions or vague verbs. The pattern is immediately predictable.

    Tool Count5/5

    13 tools is appropriate for a database connector covering base/table discovery, schema introspection, record CRUD, querying, and link management. Each tool earns its place.

    Completeness4/5

    Core workflows are well-covered: explore bases/tables/schema, then create/update/delete/query records and manage links. Minor gaps include no create/delete base or table, but these may be outside the connector's scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues