Natural Context Provider

Name: Natural Context Provider
Author: portel-dev

@portel-dev

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

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

portel-dev

投稿者

Arul Kumaran

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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.