Xperience Community MCP Server

ASP.NET Core MCP server for Xperience by Kentico projects. Exposed over MCP by the xperience community mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Why use this library? By exposing a discrete set of documented tools to an AI agent in an Xperience by Kentico project, that agent has more well structured context and capabilities. This means it can be a better copilot to developers building features for marketers using Xperience by Kentico.

Its toolset

Everything the assistant can do here goes through one of these:

• Dependencies — The Dependencies tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Xperience Community's toolset — Dependencies — is a fair guide to whether it matches your workflow. It is maintained by seangwright; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the xperience community mcp server does with a few real requests.