Schema | NCP - Natural Context Provider

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Capabilities

Features and capabilities supported by this server

Capability	Details
`tools`	{}
`logging`	{}
`prompts`	{}
`resources`	{}
`completions`	{}
`experimental`	{ "roots": { "listChanged": true }, "sampling": {}, "elicitation": {} }

Tools

Functions exposed to the LLM to take actions

Name	Description
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 })

Name

Description

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 })

Prompts

Interactive templates invoked by user choice

Name	Description
`confirm_add_mcp`	Request user confirmation before adding a new MCP server
`confirm_remove_mcp`	Request user confirmation before removing an MCP server
`configure_mcp`	Request user input for MCP configuration (env vars, args)
`approve_dangerous_operation`	Request approval for potentially dangerous operations
`confirm_operation`	Request user confirmation before executing modifier operations

Resources

Contextual data attached and managed by the client

Name	Description
`NCP Getting Started Guide`	Learn how to use NCP effectively - search tips, parameters, and best practices
`MCP Health Dashboard`	Shows health status of all configured MCPs
`Last Auto-Import Summary`	Shows MCPs imported from Claude Desktop on last startup

NCP - Natural Context Provider

Server Configuration

Capabilities

Tools

Prompts

Resources

Latest Blog Posts

MCP directory API