Nexus MCP
Related Servers
Alternatives to Nexus MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude and other MCP clients to list and query allowlisted Supabase tables, insert rows, and search, read, or create Notion pages. It ships with table allowlists, validated inputs, row limits, and an optional read-only mode that unregisters write tools, plus a mock mode for trying it without credentials.61MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to safely interact with Supabase through read-only and gated-write tools, with bounded queries, allowlists, and explicit project targeting.-
- FlicenseAqualityCmaintenanceEnables LLM agents to read and modify company data from Notion and Supabase, with human-in-the-loop approval for all write and delete operations.5-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to read and write a Notion workspace through a single token, covering pages, databases, blocks, comments, templates, and file uploads. It keeps the model's context small by exposing three tools and fetching operation schemas on demand, while supporting batched, idempotent mutations and headless use in CI or self-hosted deployments.5,456 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI clients token-authenticated read/write access to Notion, letting them create and rewrite pages, query databases, append blocks, apply templates, comment, and upload files through natural language. It exposes 47 operations behind only three tools to keep context usage small, and runs headless with batched mutations, idempotency keys, and retry on rate limits.5,456 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents and coding assistants read/write access to Notion — creating and editing pages, querying databases, appending blocks, applying templates, commenting, and uploading files — through just three context-efficient tools. It authenticates with a single token so it works headless in automation, CI, and self-hosted deployments, with batched mutations, idempotency keys, and retry handling built in.5,456 npmMIT
TDQS
Scored across 3 tools
health_check is clearly distinct (concurrent probing with latency), but server_info and list_sources both surface information about connected data sources, creating a potential misselection point. Descriptions mitigate this by framing server_info as config/version/write-flags and list_sources as per-source capabilities.
All names are readable two-word snake_case, but two are noun-first (server_info, health_check) while one is verb-first (list_sources). Minor deviation from a single predictable pattern, not enough to cause confusion.
Three tools is thin even for a metadata/diagnostics server; server_info and list_sources could plausibly be merged. Each tool still has a defensible purpose, so it is borderline rather than mismatched.
The surface stops at introspection: there is no tool to actually query or interact with the configured data sources, and no tool to inspect individual source capabilities or configuration in depth beyond a list. An agent that needs data (not just status) hits a dead end.