DevHub CMS MCP Server Integration

What does “DevHub CMS” MCP Server do?

The DevHub CMS MCP (Model Context Protocol) Server acts as an integration layer that connects AI assistants and large language models (LLMs) to the DevHub CMS system. By leveraging the Model Context Protocol, this server enables AI clients to manage and interact with DevHub CMS content, such as querying businesses and handling content management workflows. This integration allows developers to use AI agents for tasks like retrieving business information, managing locations, and performing content operations via standardized APIs. As a result, it streamlines content management workflows, enhances automation, and provides a unified interface for AI-driven development and CMS administration.

List of Prompts

No prompt templates are mentioned in the repository.

List of Resources

No specific resources are documented in the repository.

List of Tools

• get_businesses(): Retrieves all businesses within the DevHub account, returning a list of businesses along with their IDs and names.

Use Cases of this MCP Server

• Business Directory Management: Easily retrieve and list all businesses managed within a DevHub CMS account, enabling LLMs or assistants to surface up-to-date business information.
• AI-powered Content Management: Integrate AI workflows with CMS operations, allowing automated queries and streamlined content management for business data.
• Location Management Automation: (Implied by the section header) Potentially manage and interact with business locations via AI, reducing manual database queries.
• Multi-platform Integration: Deploy the DevHub CMS MCP on various platforms (Claude, Cursor, Smithery), making it adaptable for different AI-driven workflows.
• Secure API Access: Leverage environment-based API key handling to enable secure programmatic access to the DevHub CMS via LLMs.

How to set it up

Windsurf

No Windsurf-specific instructions found.

Claude

1. Ensure you have the uv package manager installed.
2. Locate your claude_desktop_config.json file.
3. Add the following configuration under the mcpServers object:

   {
       "mcpServers": {
           "devhub_cms_mcp": {
               "command": "uvx",
               "args": [
                   "devhub-cms-mcp"
               ],
               "env": {
                   "DEVHUB_API_KEY": "YOUR_KEY_HERE",
                   "DEVHUB_API_SECRET": "YOUR_SECRET_HERE",
                   "DEVHUB_BASE_URL": "https://yourbrand.cloudfrontend.net"
               }
           }
       }
   }
   

4. Save the file and restart Claude Desktop.
5. Verify that the server is available in the Claude Desktop interface.

Securing API keys:
Environment variables are set in the env field as shown above.

Cursor

1. Open Cursor global configuration or the relevant project settings.
2. Add the following configuration to your MCP servers section:

   {
       "mcpServers": {
           "devhub_cms_mcp": {
               "command": "uvx",
               "args": [
                   "devhub-cms-mcp"
               ],
               "env": {
                   "DEVHUB_API_KEY": "YOUR_KEY_HERE",
                   "DEVHUB_API_SECRET": "YOUR_SECRET_HERE",
                   "DEVHUB_BASE_URL": "https://yourbrand.cloudfrontend.net"
               }
           }
       }
   }
   

3. Save and restart Cursor if necessary.
4. Confirm access to DevHub CMS MCP tools within Cursor.

Securing API keys:
Environment variables are set in the env field as shown above.

Cline

No Cline-specific instructions found.

Smithery

1. Open your terminal.
2. Run the install command:

   npx -y @smithery/cli install @devhub/devhub-cms-mcp --client claude
   

3. Follow prompts to complete installation.
4. Verify that the MCP server appears in your Claude Desktop or Smithery interface.

Securing API keys:
Handled via environment variables when launching the service.

Claude Code

1. Use the Claude Code CLI to add the MCP server:

   claude mcp add devhub-cms-mcp \
       -e DEVHUB_API_KEY=YOUR_KEY_HERE \
       -e DEVHUB_API_SECRET=YOUR_SECRET_HERE \
       -e DEVHUB_BASE_URL=https://yourbrand.cloudfrontend.net \
       -- uvx devhub-cms-mcp
   

2. The environment variables are securely passed to the MCP server.

Example JSON configuration with environment variables

{
    "mcpServers": {
        "devhub_cms_mcp": {
            "command": "uvx",
            "args": [
                "devhub-cms-mcp"
            ],
            "env": {
                "DEVHUB_API_KEY": "YOUR_KEY_HERE",
                "DEVHUB_API_SECRET": "YOUR_SECRET_HERE",
                "DEVHUB_BASE_URL": "https://yourbrand.cloudfrontend.net"
            }
        }
    }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "devhub_cms_mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “devhub_cms_mcp” to whatever the actual name of your MCP server is and replace the URL with your own MCP server deployment.

Overview

Between these tables:
This MCP server provides basic integration with clear installation instructions and one documented tool but lacks prompt templates, explicit resources, root, and sampling support. Based on comprehensiveness and utility, we would rate this MCP integration a 5/10.

MCP Score