Nexus-MCP Knowledge Search

    1

    Search Notion and Supabase knowledge through your configured Nexus-MCP server using AI agents, with secure defaults and clear setup instructions.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Nexus-MCP Knowledge Search

    Example session with this skill installed

    Find the latest database migration instructions in Notion and Supabase, then compare them for any discrepancies in the table naming conventions.

    • Read your context and instructions
    • Compiled the nexus-mcp knowledge search

    I have searched your connected Notion and Supabase knowledge bases using the Nexus-MCP server. Below is a comparison of the migration instructions retrieved from both sources.

    Knowledge Base Comparison: Migration Instructions

    FeatureNotion (Project Docs)Supabase (Migrations Table)Discrepancy Found
    Latest Entry2023-11-14-add-user-profiles2023-11-15-auth-cleanupYes: Supabase is ahead
    Naming Conventionkebab-casekebab-caseNo
    Table Prefixtbl_public.Yes: Notion uses legacy prefix
    Primary Key PolicyUUID v4UUID v4No
    Audit Columnscreated_at, updated_atcreated_at onlyYes: Notion expects updated_at

    Detailed Findings

    Notion Source: The "Engineering Wiki" contains a document titled "Database Standards v2" which still references a tbl_ prefix for new relations.

    Supabase Source: The actual migrations table reflects the current production state where the public. schema is used without the tbl_ prefix.

    Inference: The documentation in Notion appears to be out of date regarding the current schema naming conventions used in the actual Supabase migrations.

    Next steps

    1. Update the "Database Standards v2" page in Notion to remove the tbl_ prefix requirement.
    2. Verify if the missing updated_at columns in the Supabase migration were intentional or a missed requirement.
    3. Run npx nexus-mcp sync if you wish to refresh the local tool index.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Developers managing knowledge across disparate silos like Notion and Supabase often struggle with retrieval latency and context switching. This skill provides a structured workflow for AI agents to interface with an existing Nexus-MCP server, enabling unified search across internal documentation and databases.

    What it does

    • Multi-source search query both Notion pages and Supabase records through a single interface.
    • Contextual synthesis summarize findings from multiple sources while clearly distinguishing between facts and inferences.
    • Source attribution include specific titles and identifiers provided by the MCP tools for every result.
    • Safe retrieval prioritize read-only operations to prevent accidental data modification during search.

    How it works

    1. Identify the specific project, date range, or keywords the user needs to find.
    2. Inspect the available Nexus-MCP tools exposed by the local environment to determine specific search capabilities.
    3. Query the connected Notion and Supabase instances using the relevant read-only tools.
    4. Report a consolidated summary of the findings or provide troubleshooting steps if the server is unreachable.

    Frameworks & tools

    Requires a functional Nexus-MCP server installation and an AI client that supports MCP tools. Designed for environments integrating Notion and Supabase.

    Why this beats prompting it yourself

    Standard prompts often hallucinate search results or fail to distinguish between multiple documentation sources. This skill enforces a strict verification loop, ensuring the agent only reports data actually returned by the Nexus-MCP server while maintaining read-only safety by default.

    Use cases

    • Compare deployment notes in Notion with historical migration records in Supabase.
    • Locate specific onboarding documentation across multiple internal workspaces.
    • Retrieve and summarize project-specific database schemas for new team members.

    Known limitations

    Does not include the Nexus-MCP server, credentials, or databases. Depends entirely on the user's local MCP configuration and tool availability within their AI client.

    Requires pre-configured Nexus-MCP server and active Notion/Supabase connections. Cannot fix local environment authentication or network errors.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    • Free with an Agensi account

    Requires

    Nexus MCP

    Permissions

    Network Access
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a specialized logic layer that allows your AI agent to effectively communicate with a Nexus-MCP server to search and compare data across Notion and Supabase simultaneously.

    No, the Nexus-MCP server, API credentials, and databases must be configured separately. This skill provides the structured workflow and logic needed for your AI agent to interact with those existing tools.

    This skill is compatible with any AI client or agent environment that supports the Model Context Protocol (MCP) and has access to a configured Nexus-MCP server.

    The skill is designed with a "read-only" priority, meaning it is programmed to use retrieval tools specifically to prevent accidental deletions or edits to your internal documentation and records.

    By enforcing a strict verification loop, the skill ensures the agent only reports data actually returned by the server, significantly reducing the risk of hallucinations common in standard prompting.

    New in LLM Ops