Helpjuice MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELPJUICE_ACCOUNT | Yes | Your subdomain, e.g. yourcompany for yourcompany.helpjuice.com | |
| HELPJUICE_API_KEY | Yes | Your Helpjuice API key | |
| HELPJUICE_BASE_URL | No | Override the Helpjuice API base URL for testing | https://<account>.helpjuice.com/api/v3 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledge_baseA | Full-text search across the Helpjuice knowledge base. Returns matching articles with a short text sample. Use get_article to read the full answer before quoting it. |
| get_articleA | Read one article. Returns the body as clean plain text by default (internal blocks expanded), or as HTML for editing. |
| list_articlesB | List articles with filters (category, published, visibility, created/updated dates, language). Returns compact rows. |
| find_stale_articlesA | Find published articles that have not been updated in N days (default 180), oldest first. Useful for content audits before a release. |
| create_articleA | Create a new article. Saved as an unpublished draft unless published=true. body accepts HTML or plain text (blank lines become paragraphs). |
| update_articleA | Update an article's title, body, summary, categories or published state. Only the fields you pass are changed. Read the article first with get_article(format='html') when editing the body. |
| delete_articleA | Delete an article from the knowledge base. Confirm with the user first; consider unpublishing instead. |
| list_categoriesA | List knowledge base categories (id, name, parent, visibility, article counts). |
| get_categoryA | Get one category with its published and draft articles. |
| create_categoryC | Create a knowledge base category, optionally nested under a parent. |
| list_recent_activityA | Recent knowledge base activity (who created, edited or published what), newest first. |
| get_accountA | Get the knowledge base account settings (name, subdomain, internal KB flag, contact email). |
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 12 tools
Most tools target clearly distinct actions and resources, with article CRUD, category listing/creation, and account/activity reads separated well. The main possible confusion is between search_knowledge_base, list_articles, and find_stale_articles, though their descriptions clarify the intended use cases.
All tool names follow a consistent snake_case verb_noun pattern such as search_knowledge_base, get_article, list_articles, create_article, and delete_article. The convention is predictable throughout the set.
Twelve tools is well-scoped for a knowledge base server, covering article and category management plus search and activity inspection. No tool appears redundant or gratuitous at the surface level.
Article lifecycle coverage is strong with search, read, list, create, update, delete, and stale-content auditing. Category management is less complete because categories can be listed, fetched, and created but not updated or deleted.