NCP - Natural Context Provider
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
| completions | {} |
| experimental | {
"roots": {
"listChanged": true
},
"sampling": {},
"elicitation": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| findA | 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"). |
| codeA | 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 }
FALLBACK - Direct namespace calls (when you know exact tools):
|
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 |
TDQS
Scored across 2 tools
find and code have clearly distinct purposes: one for discovering/listing tools, the other for executing TypeScript code. There is no ambiguity about which tool to use for a given task.
Both tool names are lowercase single words, so the style is consistent. However, the names are vague and do not follow a descriptive verb_noun convention like search_tools or execute_code.
With only two tools, the server feels thin, but as a meta-tool that can execute arbitrary code, it could be reasonably scoped. Still, two tools is on the low end and likely limits direct usability.
The server advertises ncp.do and direct namespace calls, but these are not exposed as actual tools. The only way to invoke external tools is through the code tool, which is a significant gap for a provider that claims to make tool invocation natural. Basic operations like retrieving a specific tool's schema or directly calling a tool are missing.