Skip to main content
Glama
devhub

DevHub CMS MCP

Official
by devhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_hours_of_operationA

Get the hours of operation for a DevHub location

Returns a list of items representing days of the week

Except for the special case formatting, this object is a list of 7 items which represent each day.

Each day can can have one-four time ranges. For example, two time ranges denotes a "lunch-break". No time ranges denotes closed.

Examples:
9am-5pm [["09:00:00", "17:00:00"]]
9am-12pm and 1pm-5pm [["09:00:00", "12:00:00"], ["13:00:00", "17:00:00"]]
Closed - an empty list []

Args:
    location_id: DevHub Location ID
    hours_type: Defaults to 'primary' unless the user specifies a different type
get_businessesA

Get all businesses within the DevHub account

Returns a list of businesses with the following fields:
- id: Business ID that can be used in the other tools
- business_name: Business name

If only one business exists in the account, you can assume that the user wants to use that business for any business_id related tools.
get_locationsB

Get all locations for a business

Returns a list of locations with the following fields:
- id: Location ID that can be used in the other tools
- location_name: Location name
- location_url: Location URL in DevHub
- street: Street address
- city: City
- state: State
- country: Country
- postal_code: Postal code
- lat: Latitude
- lon: Longitude
update_hoursA

Update the hours of operation for a DevHub location

Send a list of items representing days of the week

Except for the special case formatting, this object is a list of 7 items which represent each day.

Each day can can have one-four time ranges. For example, two time ranges denotes a "lunch-break". No time ranges denotes closed.

Examples:
9am-5pm [["09:00:00", "17:00:00"]]
9am-12pm and 1pm-5pm [["09:00:00", "12:00:00"], ["13:00:00", "17:00:00"]]
Closed - an empty list []

Args:
    location_id: DevHub Location ID
    new_hours: Structured format of the new hours
    hours_type: Defaults to 'primary' unless the user specifies a different type
site_from_urlA

Get the DevHub site ID from a URL.

Can prompt the user for the URL instead of passing a site_id.

Returns details about the Site matches the URL that can be used in the other tools.
- Site ID: ID of the DevHub site
- Site URL: URL of the DevHub site
- Site Location IDs: List of location IDs associated with the site

Args:
    url: URL of the DevHub site, all lowercase and ends with a slash
upload_imageB

Upload an image to the DevHub media gallery

Supports webp, jpeg and png images

Args:
    base64_image_content: Base 64 encoded content of the image file
    filename: Filename including the extension
get_blog_postC

Get a single blog post

Args:
    post_id: Blog post id
create_blog_postB

Create a new blog post

Args:
    site_id: Website ID where the post will be published. Prompt the user for this ID.
    title: Blog post title
    content: HTML content of blog post. Should not include a <h1> tag, only h2+
update_blog_postC

Update a single blog post

Args:
    post_id: Blog post ID
    title: Blog post title
    content: HTML content of blog post. Should not include a <h1> tag, only h2+
get_nearest_locationB

Get the nearest DevHub location

Args:
    business_id: DevHub Business ID associated with the location. Prompt the user for this ID
    latitude: Latitude of the location
    longitude: Longitude of the location

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have distinct purposes, but get_hours_of_operation and update_hours are closely related and could potentially be confused due to similar naming and overlapping functionality. The other tools target clearly different resources like blog posts, businesses, locations, and images, making them easy to distinguish.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern, such as create_blog_post, get_blog_post, update_blog_post, get_businesses, get_locations, and upload_image. There are no deviations in style or convention, making the set predictable and readable.

Tool Count5/5

With 10 tools, the count is well-scoped for a CMS server covering blog posts, businesses, locations, hours, and media. Each tool serves a clear purpose, and there are no redundant or trivial additions, fitting typical expectations for such a domain.

Completeness3/5

The toolset covers blog post creation, retrieval, and update, but lacks deletion, which is a notable gap in the CRUD lifecycle. For locations and businesses, retrieval tools are present, but creation, update, and deletion are missing, leaving significant operational gaps that could hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources