NCP - Natural Context Provider (NCP)
NCP - Natural Context Provider (NCP) Details
NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.
Use Case
NCP acts as a single entry point to discover and execute tools across multiple MCPs, skills, and Photons. It enables semantic tool discovery with the find command, code-mode execution for composing multi-step TypeScript workflows, and run for executing tools individually. It also supports scheduling, so you can automate recurring tasks. Example usage includes discovering the right tool with find, writing a TypeScript workflow with code that calls tools such as web.search and filesystem read_file, and then scheduling that workflow to run on a schedule. Example from docs: const results = await web.search({ query: "Model Context Protocol conference 2025" }); for (const url of results) { const content = await web.read({ url }); } These patterns show how to integrate external MCPs like filesystem, github, brave-search, and web photon capabilities into a cohesive automation and AI-workflow surface.
Available Tools (14)
Examples & Tutorials
Real example code and usage patterns directly from the documentation:
<h1 class="text-2xl font-semibold mt-5 mb-3">Install NCP</h1>
npm install -g @portel/ncp<h1 class="text-2xl font-semibold mt-5 mb-3">Import existing MCPs (optional)</h1>
ncp config import # Paste your config JSON when prompted<h1 class="text-2xl font-semibold mt-5 mb-3">Configure your MCP client</h1>
{
"mcpServers": {
"ncp": {
"command": "ncp"
}
}
}<h1 class="text-2xl font-semibold mt-5 mb-3">Quick Example: General CLI usage</h1>
<h1 class="text-2xl font-semibold mt-5 mb-3">See your imported MCPs</h1>
ncp list<h1 class="text-2xl font-semibold mt-5 mb-3">Direct testing example from docs</h1>
ncp run filesystem read_file --path "/tmp/test.txt"// A Real Example from the docs
// Search the web for MCP conferences
const results = await web.search({
query: "Model Context Protocol conference 2025"
});// Read each result
for (const url of results) {
const content = await web.read({ url });
// Save to ~/.ncp/mcp-conferences.csv
}
<h1 class="text-2xl font-semibold mt-5 mb-3">Scheduling example from docs</h1>
ncp schedule create code:run "every day at 9am" \
--name "MCP Conference Scraper" \
--catchup-missedInstallation Guide
Step-by-step from the documentation:
1) Install NCP globally
npm install -g @portel/ncp2) Import existing MCPs (optional)
ncp config import # Paste your config JSON when prompted3) Configure your MCP client with a sample config:
{
"mcpServers": {
"ncp": {
"command": "ncp"
}
}
}4) Verify installed tools
ncp listIntegration Guides
Frequently Asked Questions
Is this your MCP?
Claim ownership and get verified badge
Sponsored
Key notes from the docs: - NCP provides a single, unified interface for MCPs, skills, and Photons. - On-demand loading and code-mode execution help reduce token usage and improve responsiveness. - There is an emphasis on vendor-agnostic, plug-and-play MCPs; integrate via the CLI and standard JSON configs. - You can import MCPs, and then configure clients to see only NCP as the tool surface in the AI client.
Node.js 18+ (Node.js 18.x recommended), npm (included with Node.js) or npx for running packages, and command line access (Terminal on Mac/Linux, Command Prompt/PowerShell on Windows).
Compare Alternatives
Similar MCP Tools
9 related toolsPlaywright MCP
Playwright MCP server. A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables large language models (LLMs) to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. The server is designed to be fast, lightweight, and deterministic, offering LLM-friendly tooling and a rich set of browser automation capabilities via MCP tools. It supports standalone operation, containerized deployments, and integration with a variety of MCP clients (Claude Desktop, VS Code, Copilot, Cursor, Goose, Windsurf, and others).
Sequential Thinking MCP Server
Sequential Thinking MCP Server provides a dedicated MCP tool that guides problem-solving through a structured, step-by-step thinking process. It supports dynamic adjustment of the number of thoughts and allows revision and branching within a controlled workflow, making it ideal for complex analysis and solution hypothesis development. This server is designed to register a single tool, sequential_thinking, and is integrated with common MCP deployment methods (NPX, Docker) as well as editor integrations like Claude Desktop and VS Code for quick setup. The documentation provides exact configuration snippets, usage patterns, and building instructions to help you deploy and use the MCP server effectively, including Codex CLI, NPX, and Docker installation examples.
N8N MCP Server
An MCP (Model Context Protocol) server designed to integrate Claude Desktop, Claude Code, Windsurf, and Cursor with n8n workflows. This MCP enables users to build, test, and orchestrate complex workflows by exposing a set of tools that bridge Claude’s capabilities with n8n’s automation platform. The project emphasizes robust trigger handling, multi-tenant readiness, and progressive documentation to help developers understand how tools map to real-world workflow tasks. It also outlines future tooling integration points (such as getNodeEssentials and getNodeInfo) to further enhance node-structure awareness within MCP-powered automations.
Hugging Face MCP Server
Hugging Face Official MCP Server connects your large language models (LLMs) to the Hugging Face Hub and thousands of Gradio AI Applications, enabling seamless MCP (Model Context Protocol) integration across multiple transports. It supports STDIO, SSE (to be deprecated but still commonly deployed), StreamableHTTP, and StreamableHTTPJson, with the Web Application allowing dynamic tool management and status updates. This MCP server is designed to be run locally or in Docker, and it provides integrations with Claude Desktop, Claude Code, Gemini CLI (and its extension), VSCode, and Cursor, making it easy to configure and manage MCP-enabled tools and endpoints. Tools such as hf_doc_search and hf_doc_fetch can be enabled to enhance document discovery, and an optional Authenticate tool can be included to handle OAuth challenges when called.
Shadcn UI MCP Server v4
Shadcn UI v4 MCP Server is an advanced MCP (Model Context Protocol) server designed to give AI assistants comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata. It enables multi-framework support (React, Svelte, Vue, and React Native) with fast, cache-friendly access to component source code, demos, and directory structures, empowering AI-driven development workflows. The project emphasizes production-readiness with Docker Compose, SSE transport for multi-client deployments, and smart caching to optimize GitHub API usage while providing rich metadata and usage patterns for rapid prototyping and learning across frameworks.
Figma MCP server
The Figma MCP server enables design context delivery from Figma files to AI agents and code editors, empowering teams to generate code directly from design selections. It supports both a remote hosted server and a locally hosted desktop server, allowing seamless integration with popular editors through Code Connect and a suite of tools that extract design context, metadata, variables, and more. This guide covers enabling the MCP server, configuring clients (VS Code, Cursor, Claude Code, and others), and using a curated set of MCP tools to fetch structured design data for faster, more accurate code generation. It also explains best practices, prompts, and integration workflows that help teams align generated output with their design systems. The documentation includes concrete JSON examples for configuring servers in editors like VS Code and Cursor, as well as command examples for Claude Code integration and plugin installation.
MarkItDown MCP
MarkItDown-MCP is a lightweight MCP (Model Context Protocol) server provided as the markitdown-mcp package. It exposes a STDIO, Streamable HTTP, and SSE MCP server designed for calling MarkItDown to convert content to Markdown. The package focuses on simplicity and accessibility, enabling you to run the MCP server locally via a simple CLI, or in Docker for containerized workflows, with integration options for Claude Desktop. The core capability is exposed through a single tool, convert_to_markdown(uri), which accepts a URI in http:, https:, file:, or data: schemes to fetch content and convert it to Markdown. This MCP server is easy to install with pip and can be used in various transport modes, including STDIO and HTTP/SSE, making it a flexible choice for automations and integrations.
Chrome MCP Server
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search. It leverages your existing Chrome environment, including login states and configurations, to allow large language models and chatbots to control the browser natively without needing to launch a separate automation process. The project emphasizes privacy by remaining fully local and offers capabilities such as cross-tab context, streamable HTTP communication, and a built-in vector database for semantic search and content analysis. As an early-stage project, it includes a growing set of tools for browser control, inspection, and automation, with ongoing development to broaden compatibility and features.
MCP server for Appwrite docs
The MCP server for Appwrite docs enables LLMs and code-generation tools to interact with comprehensive Appwrite documentation. It empowers AI assistants to access up-to-date API references, SDK guides, and implementation examples, facilitating intelligent code generation, troubleshooting, and best-practice guidance directly from the official docs. This MCP brings real-time context, semantic search, and seamless integration with popular editors and IDEs to accelerate development workflows around Appwrite's APIs and SDKs.