Skip to main content

MCP Server

Embeddings​

In order for the MCP server to interact with the marketplace, Witboost needs to create embeddings of the marketplace instances. This feature reuses the same embedder model configured for Witty — there is no separate embedder configuration for the MCP Server.

Semantic search can be enabled, and embeddings can be (re)created, from Administration > Configuration > Marketplace. See Semantic Search for the full configuration guide.

info

Embeddings are also automatically (re)created on startup and each time a system is (un)deployed. You only need to trigger a manual creation after changing the embedder model.

Embeddings can also be (re)created programmatically:

POST /marketplace/embeddingsSearch/createEmbeddings

Authentication​

Witboost MCP server implements the OAuth 2.1 IETF standard. See MCP Auth specification for more information.

The protocol requires that the auth APIs are exposed to MCP Client that we want to support. You can configure the list of allowed origins:

In your values.yaml add these lines:

ui:
  appConfig:
    # ... other config properties ...
    backend:
        ...
        auth:
            ...
            odcr:
                ...
                cors:
                    origin: {string | string[]}

where origin is a string or array of strings specifying the allowed origins for CORS requests. This determines which domains can make authentication requests to the MCP server. (ex. "https://claude.ai")