ghl-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GHL_DOCS_DIR | No | Path to a directory containing markdown documentation files. If not set, defaults to the built-in docs directory. |
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_docsA | List loaded GoHighLevel documentation files and their endpoint/section counts. |
| search_docsA | Search GoHighLevel API docs with keyword matching across endpoints and section content. |
| list_endpointsB | List available API endpoints with optional method/path/section filters. |
| get_endpoint_detailsA | Get details for a specific API endpoint, including scope, token type, and documentation excerpt. |
| get_sectionA | Retrieve a documentation section by title or partial title. |
| get_documentA | Retrieve a full documentation file by id or title, useful for longer implementation guides and runbooks. |
| reload_docsA | Reload markdown files from disk (useful after docs updates). |
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 7 tools
Each tool has a clearly distinct purpose: listing docs, listing endpoints, searching, retrieving specific documents, sections, or endpoint details, and reloading. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_docs, get_document, search_docs). The naming is predictable and uniform.
With 7 tools, the server covers all core operations for API documentation exploration: listing, searching, retrieving at different granularities, and reloading. The count is well-scoped for its domain.
The tool set covers key workflows except for listing individual sections within a document (only counts are provided). This minor gap prevents a perfect score, but overall the surface is largely complete.