Natural Context Provider

@portel-dev

About Natural Context Provider

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.

#orchestration #vector-search #rag #token-saving #mcp-management #less-cognitive-load #reduce-clutter

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

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").

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: "[email protected]", // 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 })

Overview

What is Natural Context Provider?

Natural Context Provider (NCP) is a tool that aggregates multiple MCP servers into a single intelligent orchestrator, exposing only two tools (find and run) to the AI while handling routing, discovery, health monitoring, and semantic matching behind the scenes. It is designed for power users with multiple MCPs who want their AI to be focused, efficient, and cost-effective.

How to use Natural Context Provider?

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

Key features of Natural Context Provider

Transforms N scattered MCP servers into one orchestrator.
AI sees only two tools: find and run.
Reduces token consumption by 47–83+% depending on setup size.
Handles routing, discovery, health monitoring, and semantic matching.
2-minute setup with a single npm install command.

Use cases of Natural Context Provider

Power users with multiple MCPs whose AI becomes indecisive or picks wrong tools.
Reducing token costs and session early termination caused by tool schema overload.
Maintaining existing MCP capabilities while improving AI focus and performance.

FAQ from Natural Context Provider

How does Natural Context Provider differ from using MCPs directly?

It eliminates the paradox of too many tools by exposing only two simple tools, reducing token consumption and decision fatigue for the AI while preserving all underlying tool capabilities.

What runtime dependencies does Natural Context Provider require?

Node.js and npm are required to install the global package @portel/ncp.

Where does the tool data live?

The README does not specify data storage; NCP routes tools from existing MCP servers without centralizing data.

Are there any known limitations of Natural Context Provider?

The README does not mention limitations; it focuses on benefits and token savings.

What transport or authentication does Natural Context Provider use?

The README does not describe transport or authentication details.

Frequently asked questions

How does Natural Context Provider differ from using MCPs directly?

It eliminates the paradox of too many tools by exposing only two simple tools, reducing token consumption and decision fatigue for the AI while preserving all underlying tool capabilities.