Table of Contents

Documentation MCP Server

Query the full Dynamicweb 10 documentation from your AI assistant

The Dynamicweb Documentation MCP server exposes the full Dynamicweb 10 documentation as a queryable tool inside your AI assistant. Instead of switching to a browser and searching docs by hand, you ask your editor — "what is a PriceProvider?" — and it reads the documentation for you and answers in context.

It works for two audiences:

  • Regular users — ask plain-language questions about features, concepts, and configuration and get answers grounded in the official docs.
  • Developers — pull API references, class definitions, extensibility points, and code patterns directly into your coding assistant while you work.

This article covers what it is, how to install it, and how to use it from both angles.

What it is

Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. The Dynamicweb Documentation MCP server is an MCP endpoint backed by a DocsBot knowledge base trained on the Dynamicweb 10 documentation.

When connected, your assistant gains a search tool. Any time you ask something about Dynamicweb, the assistant can query the documentation, retrieve the relevant sections, and answer using that source material — with references back to the original articles.

The endpoint is:

https://api.docsbot.ai/teams/4E0lh5ABtrBXB6OLOAoQ/bots/TTpjMI8paZHKOt4bPkAI/mcp/

No API key or credential is required. On first connection you'll authorize once via a DocsBot consent screen and select the knowledge base to use (Dynamicweb 10 Documentation GPT). After that, it just works.

What you can use it for

The most valuable uses fall into a few buckets:

  • Concept lookups — "What is a PriceProvider?", "How does indexing work in Dynamicweb?", "What's the difference between a Feed and a Repository?"
  • Configuration help — how to set up a feature, what a setting does, where something lives in the admin
  • Extensibility and API reference — provider types, base classes, method signatures, namespaces, and the patterns to subclass or extend them
  • Code-assist grounding — while writing C# or Razor against Dynamicweb, your assistant can verify class names and APIs against the real docs instead of guessing

Installation

You can install and use the Documentation MCP server in several ways as detailed below.

Visual Studio Code

To install in VS Code:

  1. Open the MCP servers panel
  2. Add a new server with the URL above
  3. The server will show Needs Auth - click to authenticate to opens the DocsBot consent screen in your browser
  4. On the Authorize MCP Server Access screen, select Dynamicweb 10 Documentation GPT from the bot dropdown and click Allow Access
  5. The server connects and the search tool becomes available to your assistant

You can also add it via a config snippet. In your mcp.json:

{
  "servers": {
    "dynamicweb-docs": {
      "url": "https://api.docsbot.ai/teams/4E0lh5ABtrBXB6OLOAoQ/bots/TTpjMI8paZHKOt4bPkAI/mcp/"
    }
  }
}
Note

The "Needs Auth" / "Authenticating…" state is expected on first use. It's the one-time OAuth consent step where you pick the knowledge base — not a password or token you need to manage. Once authorized, the connection persists.

One-click install

Add this badge to a README or onboarding page to let users install with a single click:

[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install_Dynamicweb_Docs_MCP-0098FF?logo=visualstudiocode)](vscode:mcp/install?%7B%22name%22%3A%22dynamicweb-docs%22%2C%22url%22%3A%22https%3A%2F%2Fapi.docsbot.ai%2Fteams%2F4E0lh5ABtrBXB6OLOAoQ%2Fbots%2FTTpjMI8paZHKOt4bPkAI%2Fmcp%2F%22%7D)

Other clients

Any MCP-capable client works the same way — point it at the URL and authorize. For clients that only support stdio transport, bridge with mcp-remote:

{
  "mcpServers": {
    "dynamicweb-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.docsbot.ai/teams/4E0lh5ABtrBXB6OLOAoQ/bots/TTpjMI8paZHKOt4bPkAI/mcp/"
      ]
    }
  }
}

Using it as a regular user

You don't need to know any special commands. Ask questions in plain language, and mention Dynamicweb so the assistant knows to reach for the docs.

Example — concept question:

read dynamicweb documentation. what is a priceprovider

The assistant searches the documentation and answers:

A PriceProvider is a Dynamicweb extensibility point — a piece of code that handles product price calculation in Ecommerce. It lives in the Dynamicweb.Ecommerce.Prices namespace as an abstract base class you can subclass to control how prices are resolved. The platform ships with a DefaultPriceProvider as the out-of-the-box implementation, which you can replace or extend.

The answer comes with references back to the original documentation articles so you can read further.

More examples to try:

  • "How do I set up a product feed in Dynamicweb?"
  • "What's the difference between a paragraph and an item in Dynamicweb?"
  • "Where do I configure email marketing recipients?"
  • "Explain how the Dynamicweb indexing pipeline works."
Tip

Leading with "read the Dynamicweb documentation" or "check the docs" nudges the assistant to query the MCP server rather than answer from general knowledge.

Using it as a developer

For development work, the value is grounding your coding assistant in the real API surface so it stops inventing class names and gives you patterns that actually compile.

Example — finding the right extensibility point:

I need to apply contract-specific pricing per customer. Check the Dynamicweb docs — what should I extend and what do I override?

The assistant retrieves the PriceProvider documentation and tells you to subclass PriceProvider from Dynamicweb.Ecommerce.Prices, which methods to override, and how it's registered relative to the DefaultPriceProvider.

Example — scaffolding from a verified API:

Using the Dynamicweb documentation, write a skeleton custom PriceProvider that fetches prices from an external ERP. Include the namespace, the base class, and the method signatures I need to override.

Because the assistant pulls the actual class and signatures from the docs first, the generated skeleton matches the real platform API.

Example — verifying while coding:

While writing C# or Razor against Dynamicweb, ask mid-task:

Is OrderService the right service to load an order by ID, and what method do I call? Check the docs.

The assistant confirms the class, namespace, and method against the documentation instead of guessing — useful for the parts of the API you don't have memorized.

Patterns that work well for developers:

  • Ask for namespaces and base classes explicitly — "what namespace is X in?"
  • Ask for the override list when extending providers — "what methods do I override on X?"
  • Ground code generation — "using the docs, write…" produces far more reliable output than asking cold.
  • Use it as a fact-checker on assistant-generated code before you trust it.

Notes and limitations

  • The knowledge base reflects the published Dynamicweb 10 documentation. For undocumented internals or very recent changes, verify against source
  • The assistant decides when to call the search tool. If it answers without searching, prompt it explicitly to check the documentation
  • Answers are only as current as the underlying documentation set
Improve this doc
To top