Natural Context Provider

by portel-dev

412 downloads

Not rated

GitHub

About

One MCP to Rule Them All. NCP consolidates over 50 scattered MCP tools into two unified tools (Find & Run). Your AI goes from confused to confident with 87% fewer tokens, zero tool confusion, and 5x faster responses. Perfect for teams drowning in MCP tool sprawl.

Details

Author: portel-dev
Downloads: 412
Categories: Other, Knowledge Base

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Natural Context Provider

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

From the repository

Install globally via npm install -g @portel/ncp, then add "ncp": { "command": "ncp" } to your AI client configuration.

`find`

Search or list MCP tools. Call as find() - no prefix needed. With description param: vector search tools by capability. Without description: list all available tools. Use pipe separator for multi-query ("gmail | slack").

`code`

Execute TypeScript code with automatic tool discovery and parameter mapping. **PRIMARY METHOD - ncp.do(intent, params):** Single-call execution with embedding-based param matching. No need to know exact tool names or param schemas! ncp.do("send email", { recipient: "john@example.com", // Auto-maps to "to" title: "Meeting", // Auto-maps to "subject" message: "Let's meet" // Auto-maps to "body" }) **Returns on success:** { success: true, tool, result, paramMappings } **Returns on failure:** { success: false, tool, schema, hint } - schema shows actual params needed - hint suggests corrections - Retry with correct params! **FALLBACK - Direct namespace calls (when you know exact tools):** - ncp.find("query"): Returns Tool[] with { toolName, schema, confidence } - namespace.tool(): Direct call e.g., gmail.send_email({ to, subject, body })

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "natural context provider": {
            "ncp": {
                "command": "npx",
                "args": [
                    "@portel/ncp"
                ]
            }
        }
    }
}

McpServers

{
    "ncp": {
        "command": "npx",
        "args": [
            "@portel/ncp"
        ]
    }
}

Add NCP - 1 MCP to Rule Them All

🎯 The MCP Paradox: More Tools = Less Productivity

You added MCPs to enhance your AI's capabilities. Instead: - AI picks wrong tools ("Should I use read_file or get_file_content?") - Sessions end early ("I've reached my context limit analyzing tools") - Costs explode (50+ schemas burn tokens before work even starts) - AI becomes indecisive (used to act fast, now asks clarifying questions)

🧸 Why Too Many Toys Break the Fun

A child with one toy → Treasures it, masters it, creates endless games with it A child with 50 toys → Can't hold them all, loses pieces, gets overwhelmed, stops playing Your AI is that child. MCPs are the toys. More isn't always better.

✨ The Solution: One MCP to Rule Them All

NCP transforms N scattered MCP servers into 1 intelligent orchestrator. Your AI sees just 2 simple tools: - find - "I need to read a file" → Discovers the right tool across all your MCPs - run - Executes any tool on any MCP server seamlessly Behind the scenes, NCP manages everything: routing, discovery, health monitoring, and semantic matching.

📊 Real Results

| Your MCP Setup | Without NCP | With NCP | Token Savings | |----------------|-------------|----------|---------------| | Small (5 MCPs, 25 tools) | 15,000 tokens | 8,000 tokens | 47% saved | | Medium (15 MCPs, 75 tools) | 45,000 tokens | 12,000 tokens | 73% saved | | Large (30+ MCPs, 150+ tools) | 90,000 tokens | 15,000 tokens | 83+ saved | Translation: Same tools, same capabilities, but your AI becomes focused, efficient, and cost-effective again.

🚀 2-Minute Setup

```bash npm install -g @portel/ncp # Add to your AI client config: # "ncp": { "command": "ncp" } Perfect for: Power users with multiple MCPs who want their AI to be laser-focused instead of being overwhelmed.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

find

code

Claude Desktop / Cursor

McpServers

Add NCP - 1 MCP to Rule Them All

🎯 The MCP Paradox: More Tools = Less Productivity

🧸 Why Too Many Toys Break the Fun

✨ The Solution: One MCP to Rule Them All

📊 Real Results

🚀 2-Minute Setup

Install

More like this

Sequential Thinking

Aws Kb Retrieval Server

Memory

Filesystem

EverArt

Google Drive

`find`

`code`