Kapiti MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESSHOST_API_KEY | Yes | Your Kapiti API authentication token | |
| HEADLESSHOST_BASE_URL | No | The base URL for the Kapiti API | https://api.kapiti.com |
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
| Name | Description |
|---|---|
| pingA | Test authentication and connection to the Headlesshost API |
| healthB | Check the health status of the Headlesshost API |
| get_ref_dataC | Get system reference data and lookups |
| register_userC | Register a new user in the system with account creation |
| create_userC | Create a new user in the current account |
| get_userC | Get user details by ID |
| update_userC | Update user information |
| delete_userC | Delete a user from the system |
| get_accountB | Get current account information |
| update_accountC | Update account information |
| upload_user_profile_imageC | Upload a profile image for a user |
| upload_staging_site_fileC | Upload a file to a staging site |
| create_content_siteC | Create a new content site in the current account |
| get_content_sitesB | Get all content sites in the current account |
| get_content_siteB | Get content site details by ID |
| update_content_siteC | Update staging site information |
| delete_content_siteC | Delete a content site |
| update_staging_siteC | Update staging site information |
| delete_staging_siteC | Delete a staging site |
| publish_staging_siteC | Publish a staging site to make it live |
| get_staging_siteC | Get staging site details by ID |
| get_staging_site_pagesC | Get staging site pages by ID |
| get_staging_site_configurationC | Get staging site configuration by ID |
| get_staging_site_logsC | Change logs since last publish |
| get_published_sitesC | Get published sites for a content site |
| revert_staging_siteC | Revert a staging site to a previous state |
| clone_staging_siteC | Clone a staging site |
| create_staging_site_sectionC | Create a new section in a staging site page |
| get_staging_site_sectionC | Get details of a staging site section |
| update_staging_site_sectionC | Update a staging site section |
| delete_staging_site_sectionC | Delete a staging site section |
| publish_staging_site_sectionC | Publish a staging site section |
| revert_staging_site_sectionC | Revert a staging site section to a previous state |
| get_staging_site_section_logsB | Get logs for a staging site section since the last publish |
| create_staging_site_pageC | Create a new page in a staging site |
| get_staging_site_pageC | Get details of a staging site page |
| update_staging_site_pageC | Update a staging site page |
| delete_staging_site_pageC | Delete a staging site page |
| get_staging_site_page_logsB | Get the change logs for a staging site page since the last publish |
| get_content_site_logsC | Get the last 15 activity logs for a content site |
| get_content_site_hitsB | Get daily hits for a content site |
| get_content_site_accountsC | Get accounts associated with a content site |
| get_content_site_claimsC | Get current user claims for the content site |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api_config | Current Headlesshost API configuration and available endpoints |
| api_health | Current health status and connectivity information for the Headlesshost API |
TDQS
Scored across 43 tools
The tools are generally well-differentiated by resource (e.g., content_site, staging_site, user, account) and action (e.g., get, create, update, delete), with clear boundaries. However, some tools like 'update_content_site' and 'update_staging_site' could be confused due to similar naming and overlapping domains, and 'health' and 'ping' are both diagnostic tools that might overlap in purpose.
The naming follows a highly consistent verb_noun pattern throughout, such as 'create_content_site', 'get_staging_site_page', and 'delete_user'. All tools use snake_case uniformly, with verbs like 'create', 'get', 'update', 'delete', 'upload', 'publish', and 'revert' applied predictably across resources, making the set easy to navigate.
With 43 tools, the count is excessive for the apparent domain of content and staging site management, user and account handling, and basic diagnostics. This high number suggests over-fragmentation, such as separate tools for logs and sections, which could overwhelm agents and reduce usability despite the comprehensive coverage.
The tool set provides complete CRUD/lifecycle coverage for all key domains: content sites, staging sites (including pages, sections, and files), users, and accounts. It includes advanced operations like publishing, reverting, uploading files, and diagnostics (health/ping), with no obvious gaps that would hinder agent workflows in this context.