
concrete5-community/concretecms-mcp-server
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
A Model Context Protocol (MCP) server that integrates with Concrete CMS's REST API.
Обзор
A Model Context Protocol (MCP) server for Concrete CMS built with TypeScript. Since the MCP server uses the Concrete CMS API, you need to enable it in your Concrete CMS installation first. The Concrete CMS documentation provides an introduction to the REST API and to its configuration. When you create the API Integration in Concrete CMS (System & Settings > API > Integrations), you have to set the to the address where the MCP server receives the OAuth callback. If you run the MCP server locally (for example with Claude Desktop, or with the prebuilt .mcpb extension), the redirect URI is: 3000 is the default port: if you customize it with the HTTP_PORT setting, adjust the redirect URI accordingly. If you instead run the MCP server remotely (HTTP transport), the redirect URI is ${PUBLIC_BASE_URL}/oauth/callback — see the Remote MCP Server Guide for the details. Take note of the resulting and : you'll need them when configuring the MCP server (see Settings below).
README
Показан фрагмент оригинального README. Открыть оригинал.
Concrete CMS MCP Server
A Model Context Protocol (MCP) server for Concrete CMS built with TypeScript.
Installation
Enable API in Concrete CMS
Since the MCP server uses the Concrete CMS API, you need to enable it in your Concrete CMS installation first. The Concrete CMS documentation provides an introduction to the REST API and to its configuration.
When you create the API Integration in Concrete CMS (System & Settings > API > Integrations), you have to set the Redirect URI to the address where the MCP server receives the OAuth callback.
If you run the MCP server locally (for example with Claude Desktop, or with the prebuilt .mcpb extension), the redirect URI is:
http://localhost:3000/callback
3000 is the default port: if you customize it with the HTTP_PORT setting, adjust the redirect URI accordingly.
If you instead run the MCP server remotely (HTTP transport), the redirect URI is ${PUBLIC_BASE_URL}/oauth/callback — see the Remote MCP Server Guide for the details.
Take note of the resulting Client ID and Client Secret: you’ll need them when configuring the MCP server (see Settings below).
Install the MCP Server
Via a prebuilt extension
The easiest way to use the Concrete CMS MCP Server with Claude Desktop is to install the prebuilt .mcpb extension:
- Go to the Releases page and download the latest
concretecms-mcp-server.mcpbfile. - In Claude Desktop, navigate to Settings > Extensions.
- Click Advanced settings.
- In the Extension Developer section, click the Install Extension button and select the downloaded
concretecms-mcp-server.mcpbfile.
Claude Desktop will then ask you for the configuration (Concrete CMS URL, API client ID and secret, and scopes). See Settings below for what to enter.
From source
You have to clone this repo and compile it:
git clone https://github.com/concrete5-community/concretecms-mcp-server.git
cd concretecms-mcp-server
npm ci && npm run build
If you use Claude Desktop:
- Navigate to Settings > Extensions
- Click Advanced settings
- In the Extension Developer section, click Install Unpacked Extension
- Choose the
concretecms-mcp-serverdirectory
You can also add this MCP server via JSON. For example:
{
"mcpServers": {
"concretecms": {
"command": "node",
"args": ["/path/to/concretecms-mcp-server/dist/index.js"],
Установка
This server does not publish a one-line install command.
Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →Конфигурация
{
"mcpServers": {
"concretecms": {
"command": "node",
"args": ["/path/to/concretecms-mcp-server/dist/index.js"],
"env": {
"CONCRETE_CANONICAL_URL": "https://your-concrete.example",
"CONCRETE_API_CLIENT_ID": "YOUR_API_CLIENT_ID",
"CONCRETE_API_CLIENT_SECRET": "YOUR_API_CLIENT_SECRET",
"CONCRETE_API_SCOPE": "account:read system:info:read"
}
}
}
}