Document360 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCUMENT360_API_KEY | Yes | Your Document360 API key | |
| DOCUMENT360_BASE_URL | No | The Document360 API URL | https://apihub.document360.io |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_category_page_contentB | Get category page content by ID from Document360 |
| get_articleA | Get article by ID from Document360 |
| search_in_projectA | Search inside a project version and return related articles/categories in Document360 |
| get_categoryB | Get category by ID from Document360 |
| list_project_versionsA | List all project versions from Document360 |
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
Most tools target clearly distinct resources and actions. The only likely confusion is between get_category and get_category_page_content, since both retrieve category data by ID and the descriptions do not make the distinction explicit.
Tool names consistently follow a clear verb_noun snake_case pattern: get_*, search_in_project, and list_project_versions. The naming style is uniform and predictable, making it easy for an agent to infer the purpose of each tool.
Five tools is a well-scoped size for a read-oriented knowledge base server. Each tool covers a meaningful retrieval or search operation without unnecessary redundancy or bloat.
The set covers the core read/search workflows for articles, categories, category page content, and project versions. It lacks list-all endpoints and any mutation capabilities, but for a retrieval-focused Document360 assistant the coverage is workable.