MCP Server

DEVELOPMENT TOOLING

Separate from the browser runtime

@neural-ng/mcp-server is a Node.js development package. An MCP host starts it as a child process and exchanges JSON-RPC messages over standard input/output. Your Angular bundle never imports the server or its protocol dependencies.

Install and connect

Node.js 24 is required by the alpha package. A project-local exact version is recommended because the catalog, tool schemas and installed component version should move together.

npm install --save-dev @neural-ng/[email protected]

Generic client configuration

Place this object in the MCP configuration location expected by your editor or agent host, then restart or reload its MCP connections.

{
  "mcpServers": {
    "neural-ng": {
      "command": "npx",
      "args": ["--no-install", "neural-ng-mcp"]
    }
  }
}

One-off evaluation

npx -y @neural-ng/[email protected]

The process intentionally stays open while connected. Standard output is reserved for protocol messages; fatal startup diagnostics go to standard error.

Component discovery tools

Discovery uses a generated local catalog. Search and recommendation are deterministic text/intent matching; no second model or remote service is invoked.

{
  "query": "localized date range input",
  "limit": 5
}

{
  "component": "neural-date-picker"
}

{
  "goal": "nullable inherited permission checkbox",
  "limit": 3
}

Compact theme tools

Theme tools operate on a small schema-versioned recipe rather than sending the complete resolved Core and Editor token graph through model context. Neutral is the release baseline; Glass, Mist and Futuristic are experimental preview inputs.

{
  "name": "violet-workspace",
  "options_json": "{\"preset\":\"neutral\",\"primary\":\"#7c3aed\",\"radius\":\"large\"}"
}

{
  "recipe_json": "{\"schemaVersion\":1,\"name\":\"violet-workspace\",\"extends\":\"neutral\"}",
  "patch_json": "{\"set\":{\"color.primary\":\"#7c3aed\",\"shape.radius\":\"large\"}}"
}

Resources are addressable context

Resources expose package-wide catalogs and per-component documents. Component URIs are generated for every public catalog entry, so the list grows with the library while URI structure stays predictable.

neural://catalog
neural://package/exports
neural://components/button/contract
neural://components/button/readme
neural://components/button/llms

neural://themes/catalog
neural://themes/schema
neural://themes/presets
neural://themes/presets/neutral
neural://themes/ai-guide

Token-efficient agent workflow

Start narrow and expand context only when necessary. A contract usually answers import and model questions; loading every README before choosing a component wastes context and increases conflicting guidance.

1. Call search_components with the user's intent.
2. Call get_component_contract for the selected result.
3. Read neural://components/{id}/llms for strict usage rules.
4. Import the exact entryPoint and use the returned selector/models.
5. Read the README only when examples or deeper behavior are required.
6. Never invent an input, output, class name or compatibility alias.

Results and domain errors

Successful tools return pretty-printed JSON in one text content block. Invalid component references, malformed JSON and rejected theme values return isError: true with a human-readable message.

{
  "content": [
    {
      "type": "text",
      "text": "{\n  \"matches\": [\n    \"...\"\n  ]\n}"
    }
  ]
}

// Domain or validation failure:
{
  "isError": true,
  "content": [
    {
      "type": "text",
      "text": "Unknown NeuralNg component: ..."
    }
  ]
}

Read-only security boundary

Every tool declares readOnlyHint: true, destructiveHint: false, idempotentHint: true and openWorldHint: false. These annotations help clients describe risk; the implementation also enforces the boundary by exposing no write or external I/O operation.

MCP annotations are descriptive hints, not a sandbox. Pin trusted packages and let the client apply its own process, filesystem and network controls.

Keep package versions aligned

The generated catalog describes the version shipped inside the MCP package. Pin the same NeuralNg prerelease family in the project and restart the MCP process after upgrades so the agent does not reason from an older contract.

Troubleshooting