HubSpot CMS Website MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_topicsA | List all available information topics and their documents |
| get_documentB | Get a specific document from a topic |
| get_topicC | Get all documents from a specific topic |
| searchB | Search across all documents for a query |
| get_indexA | Get the main index/overview of all available information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: getting a specific document, getting an overview, getting documents by topic, listing topics, and searching across all documents. No overlap.
All tools follow a consistent verb_noun snake_case pattern (get_document, get_index, get_topic, list_topics, search). Even 'search' fits as a verb-only name.
Five tools is well-scoped for a documentation/knowledge base server; each tool covers a necessary retrieval operation without being too few or too many.
The set covers all basic retrieval needs (single document, topic, index, listing, search). No create/update/delete operations, but that is appropriate for a read-only CMS documentation server.