Modern AI integration is shifting away from embeddings and static context toward direct, structured access to authoritative sources. Wisej.NET supports this approach by exposing the documentation through MCP (Model Context Protocol) endpoints, making it immediately consumable by AI systems.

What is MCP—and why it matters

MCP (Model Context Protocol) is a standard that allows LLMs to interact with external systems—documentation, APIs, and services—through a structured interface. Instead of injecting large amounts of text into prompts, the AI can:

• Discover available tools
• Query documentation in real time
• Navigate structured content
• Extract precise information

This results in more accurate, maintainable, and scalable AI integrations.

Wisej.NET + MCP: Direct access to the Wisej.NET documentation

The Wisej.NET documentation is available through MCP endpoints, allowing any compatible AI client—including Wisej.AI—to access it directly. For example, using Wisej.AI, integration is straightforward:

this.smartPrompt1.UseTools(new McpToolsClient("https://docs.wisej.com/docs/~gitbook/mcp"));

Once connected, the AI can discover and use the documentation endpoints as tools—without custom parsing, scraping, or indexing.

Why expose the Wisej.NET documentation through MCP

This approach avoids the typical complexity of AI integrations:

• Accurate, source-based answers
  The AI queries the official Wisej.NET documentation directly.
• No RAG pipelines
  No embeddings, indexing, or synchronization required.
• Structured interaction
  Documentation is exposed as resources and tools, not raw HTML.
• Always up to date
  The AI works with the latest published documentation.
• Seamless integration with Wisej.AI
  Results can be used immediately within the application:
  • Generate code
  • Assist developers
  • Drive workflows

Wisej.NET MCP Documentation Endpoints

Each section of the Wisej.NET documentation is exposed through its own MCP endpoint.

Core Documentation

Core concepts, controls, and architectural patterns in Wisej.NET.

• Docs: https://docs.wisej.com/docs
• MCP: https://docs.wisej.com/docs/~gitbook/mcp

API Reference

Complete API surface: classes, properties, methods, and events.

• Docs: https://docs.wisej.com/api
• MCP: https://docs.wisej.com/api/~gitbook/mcp

AI (Wisej.AI)

AI components, SmartPrompt, SmartHub, tool system, and MCP integration.

• Docs: https://docs.wisej.com/ai
• MCP: https://docs.wisej.com/ai/~gitbook/mcp

Theme Builder

Theme system, styling variables, and UI customization.

• Docs: https://docs.wisej.com/theme-builder
• MCP: https://docs.wisej.com/theme-builder/~gitbook/mcp

Deployment

Hosting, IIS configuration, cloud deployment, and production setup.

• Docs: https://docs.wisej.com/deployment
• MCP: https://docs.wisej.com/deployment/~gitbook/mcp

Hybrid Applications

Mobile and hybrid application deployment (iOS and Android).

• Docs: https://docs.wisej.com/hybrid
• MCP: https://docs.wisej.com/hybrid/~gitbook/mcp

Extensions

Custom components, integrations, and extension libraries.

• Docs: https://docs.wisej.com/extensions
• MCP: https://docs.wisej.com/extensions/~gitbook/mcp

What the MCP endpoints provide

Each endpoint exposes structured capabilities that AI systems can use directly:

Resources

Documentation pages and structured content.

Tools

Capabilities such as:

• Searching documentation
• Retrieving sections
• Extracting relevant details

Prompts (when available)

Guided interactions for navigating documentation.

How it works in a Wisej.NET application

1. A user asks a question
2. Wisej.AI receives the request
3. MCP endpoints are discovered automatically
4. The AI queries the Wisej.NET documentation
5. A grounded response is generated

The result can then:

• Generate Wisej.NET code
• Assist developers in real time
• Integrate directly into the UI

Real-world use cases

Developer copilots

AI generates correct Wisej.NET code using the official documentation.

Smart help systems

Interactive documentation embedded in applications.

API-aware assistants

Precise answers using actual API definitions.

Guided development workflows

AI-assisted implementation using official patterns.

Strategic takeaway

By exposing the Wisej.NET documentation through MCP endpoints, Wisej.NET enables:

• Direct AI access to authoritative sources
• Elimination of RAG complexity
• Structured, tool-based interaction

This transforms documentation from a static reference into a live, queryable knowledge source for AI

Final thought

MCP is emerging as the standard way AI systems interact with external knowledge and tools.

Wisej.NET embraces this by making the Wisej.NET documentation directly accessible through MCP—ready to be consumed by AI systems without additional infrastructure.