Integration

Document360 integration

Document360 is a knowledge base platform. With its v3 API, list projects and workspaces, then create, update, fork, publish, unpublish, archive and delete articles and categories (create, update, publish and unpublish also in bulk), read their versions, settings, labels, comments and attachments, search a workspace or ask its AI search, manage Drive folders and files, glossary entries, snippets, variables, labels and tags, mirror articles, invite and manage team accounts and readers and their groups, track translations, start project exports and imports, and read knowledge-base analytics. The analytics routes and the routes that create, change or delete team accounts, readers and reader groups belong to Document360's premium API add-on and answer 403 without it. Left out: content-access permission rules, custom roles and permission matrices, team group administration, site custom scripts, redirection rules, irreversible bulk deletions, API reference (OpenAPI file) imports, analytics timelines and the visits-by-country breakdown, bulk mirroring, AI writer style guides, article template authoring, Drive file tags and Drive uploads (the file field of that multipart route is not documented). Every tool takes the project_id that list_projects returns. Most tools that create, publish or fork content require the user_id of a team account (from list_users), because an API key identifies no person. Authentication is a v3 API key (d360_sk_..., created under Settings > Knowledge base portal > API keys; v1/v2 API tokens do not work) sent in the X-API-Key header, plus the API host of the project's region (Europe, United States or Canada).

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Document360.Built from the 154 Document360 tools below, on the connection you add once.

What you can do with Document360

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Article, 6 operations

  • create_articleCreate articlePOSTCreates a new article as a draft in the given workspace and category; user_id is required with an API key. Publish the draft with publish_article to make it visible to readers.
  • delete_articleDelete articleDELETEPermanently deletes the article and all its versions. This action is irreversible. Consider unpublishing or hiding the article instead if it may need to be restored later.
  • get_articleGet articleGETReturns the latest version of the article (draft or published). To retrieve a specific version, use `get_article_version` instead. The response includes both raw content and rendered HTML.
  • get_article_analyticsGet article analyticsGETReturns all-time engagement metrics and project link count for a single article. The metrics include views, reads, likes, dislikes, time spent, and feedback count.
  • list_articles_with_feedbackList articles with feedbackGETReturns a paginated list of articles with their feedback metrics (likes, dislikes, total feedbacks, views).
  • list_workspace_articlesList workspace articlesGETReturns a paginated list of article summaries within the specified workspace. Pagination is performed in-memory after fetching all articles, so large datasets may have higher latency. The `page_size` parameter accepts a maximum value of `100`.

Group, 6 operations

  • create_reader_groupCreate reader groupPOSTCreates a reader group with the given title, description, associated readers and access scope, and returns it. Part of the premium API add-on.
  • delete_reader_groupDelete reader groupDELETEPermanently deletes the specified reader group after validating that it exists. This action cannot be undone; readers previously associated with the group will lose their group membership but are not themselves deleted.
  • get_reader_groupGet reader groupGETRetrieves detailed information about a reader group, including its associated readers and access scope configuration. The endpoint validates that the group exists before fetching its details; if the group ID is invalid, a `404` error is returned.
  • get_user_groupGet user groupGETReturns the group's details, portal role, and members. Returns `404 Not Found` if the group does not exist. Use `page`/`page_size` and `search` to page and filter the member list.
  • list_reader_groupsList reader groupsGETReturns all reader groups for the specified project. The response is currently unpaginated and returns the complete list of groups in a single response.
  • list_user_groupsList user groupsGETReturns all user groups for the project. The response is currently unpaginated and returns the complete list in a single call. Each group includes its title and description.

Version, 6 operations

  • delete_article_versionDelete article versionDELETEPermanently deletes the specified version of the article. The currently published version cannot be deleted; unpublish the article first to remove it. If only one version remains, use the delete article endpoint instead. This action is irreversible.
  • delete_category_versionDelete category versionDELETEDeletes a single version of the category by version number. The last remaining version cannot be deleted; attempting to do so will result in an error. Requires `DeleteCategories` permission.
  • get_article_versionGet article versionGETRetrieves the content for a specific historical version of the article. Use `list_article_versions` to list available version numbers.
  • get_category_versionGet category versionGETRetrieves the content for a specific version number of the category. Supports both `raw` and `display` content modes, behaving identically to `get_category_content`.
  • list_article_versionsList article versionsGETReturns all versions of the article, including both draft and published versions. Each version includes its status (Draft, Published, etc.), creation date, and the user who created it. Hidden or deleted articles will not be returned.
  • list_category_versionsList category versionsGETReturns all content versions for the specified category as an unpaginated list. Each version includes a version number, status (draft or published), and creation metadata.

Label, 5 operations

  • create_labelCreate labelPOSTCreates a project-level label for the given language. The label can then be associated with articles or categories via the article/category label endpoints. Returns `422` when the project's plan label limit has been reached or the name is missing.
  • get_labelGet labelGETReturns `404` if the label does not exist or belongs to a different project.
  • list_article_labelsList article labelsGETList an article's labels.
  • list_category_labelsList category labelsGETList a category's labels.
  • list_labelsList labelsGETReturns a paginated list of every label defined on the project. Use `search` to match against the label name (case-insensitive substring).

Category, 4 operations

  • create_categoryCreate categoryPOSTCreates a new category within the specified workspace. Requires the UpdateCategories permission. user_id is required with an API key; without it the request is rejected with 422.
  • delete_categoryDelete categoryDELETEPermanently deletes a category and all of its content, including every version and any child articles. This action is irreversible and cannot be undone. Requires `DeleteCategories` permission and the caller must pass the ACL check.
  • get_categoryGet categoryGETReturns category metadata including nested articles and child categories. Requires `ViewCategories` permission and the caller must pass the ACL check for the requested category. Returns `404` if the category does not exist or the caller lacks access.
  • list_workspace_categoriesList workspace categoriesGETReturns categories as a hierarchical tree structure, where each category may contain nested `child_categories`. The response is currently unpaginated and returns all categories in the workspace.

Comment, 4 operations

  • add_article_commentAdd article commentPOSTCreates a new comment thread on an article's content. This is the second of two calls.
  • add_category_commentAdd category commentPOSTCreates a new comment thread on a page category 's content. Only page categories carry content; folder and index categories return `404`. This is the second of two calls.
  • list_article_commentsList article commentsGETReturns the comment threads on an article in a single resolution status (defaults to `open`), newest first.
  • list_category_commentsList category commentsGETReturns the comment threads on a page category (a category that carries its own page content) in a single resolution status (defaults to `open`), newest first. Only page categories support comments; folder and index categories return `404`.

File, 4 operations

  • delete_drive_fileDelete drive fileDELETEPermanently deletes a single file from the drive. This operation is irreversible. If the file is currently embedded in any articles, those references will become broken. Requires `DeleteDrive` permission.
  • get_drive_fileGet drive fileGETReturns detailed file metadata including dimensions, tags, thumbnail URL, and alternative text. The `folder_id` must match the folder that currently contains the file; otherwise the file will not be found.
  • list_article_drive_filesList article drive filesGETReturns a list of media file URLs that are embedded in the article's content body. Useful for auditing media usage or identifying orphaned files. If `lang_code` is omitted, the default project language is used.
  • move_drive_fileMove drive filePUTMoves the file from its current folder into the folder specified by `folder_id` in the URL path. The file retains its original ID and metadata. Returns `404` if the file or destination folder does not exist. Requires `UpdateDrive` permission.

Folder, 4 operations

  • create_drive_folderCreate drive folderPOSTCreates a new folder at the root level, or nested under an existing parent folder via parent_folder_id, and returns it. Requires the UpdateDrive permission.
  • delete_drive_folderDelete drive folderDELETEPermanently deletes the folder and all files contained within it. This operation is irreversible and cannot be undone. Nested subfolders and their files are also deleted. Requires `DeleteDrive` permission.
  • get_drive_folderGet drive folderGETReturns folder metadata along with a paginated list of files contained in the folder. The `page` and `page_size` parameters control file pagination only; subfolder data is always returned in full.
  • list_drive_foldersList drive foldersGETReturns all folders as a hierarchical tree structure where each folder may contain nested `sub_folders`. Requires `ViewDrive` permission. To retrieve files within a specific folder, use `get_drive_folder` instead.

Glossary, 4 operations

  • create_glossary_entryCreate glossary entryPOSTCreates a glossary entry: a term and its definition, global or per language, that articles can reference through its merge code. user_id is required with an API key.
  • delete_glossary_entryDelete glossary entryDELETEPermanently removes the glossary entry from the project. Articles that referenced the entry via its merge code will continue to contain the unresolved merge code until they are re-edited.
  • get_glossary_entryGet glossary entryGETReturns the full glossary representation including `dependency_article_count`. Returns `404` if the glossary does not exist or belongs to a different project.
  • list_glossary_entriesList glossary entriesGETReturns a paginated list of glossary summaries. Dependency-article information is omitted from list responses to keep payloads small, use `get_glossary_entry` for `dependency_article_count`.

Publish, 4 operations

  • bulk_publish_articlesBulk publish articlesPOSTPublishes up to 100 articles in a single request. Each article is published independently, if one fails, others are still processed. The response includes per-article success/failure results with details on any errors.
  • bulk_publish_categoriesBulk publish categoriesPOSTPublishes multiple categories in a single request, up to a maximum of 100 per call. Requires `PublishArticles` permission. Each category is processed independently and the response contains per-item `success` and `details` fields.
  • publish_articlePublish articlePOSTTransitions the specified article version from draft to published status, making it visible to readers. The `version_number` must reference an existing draft version.
  • publish_categoryPublish categoryPOSTPublishes the given version_number of the category, making it visible to readers. Requires the PublishArticles permission (not UpdateCategories); user_id is required with an API key.

Snippet, 4 operations

  • create_snippetCreate snippetPOSTCreates a snippet that can be referenced inside article content via its merge code.
  • delete_snippetDelete snippetDELETEPermanently removes the snippet from the project. Articles that referenced the snippet via its merge code will continue to contain the unresolved merge code until they are re-edited.
  • get_snippetGet snippetGETReturns the full snippet representation including `dependency_article_count`, the number of articles that currently reference this snippet across all languages. Returns `404` if the snippet does not exist or belongs to a different project.
  • list_snippetsList snippetsGETReturns a paginated list of snippet summaries. Dependency-article information is omitted from list responses to keep payloads small, use `get_snippet` to retrieve `dependency_article_count`.

Summary, 4 operations

  • get_ai_search_summaryGet ai search summaryGETReturns aggregate AI search metrics for the specified date range, including total queries, answered and unanswered counts, conversation count, and user feedback (likes/dislikes).
  • get_article_analytics_summaryGet article analytics summaryGETReturns aggregate article engagement data for the specified date range, including total views, reads, likes, dislikes, most-read duration, and the count of articles with at least one view. Use this endpoint to build dashboard summary tiles.
  • get_feedback_summaryGet feedback summaryGETReturns aggregate feedback metrics for the specified date range, including total likes, dislikes, feedback count, article count, and an optional breakdown of additional feedback categories.
  • get_search_summaryGet search summaryGETReturns aggregate search metrics for the specified date range, including total searches, successful searches, no-result searches, bounced searches, and success/failure rates. Use this endpoint to build search performance dashboard tiles.

User, 4 operations

  • create_userCreate userPOSTCreates a team account and sends it an invitation email. invited_by is required with an API key, which identifies no person. Part of the premium API add-on.
  • delete_userDelete userDELETEPermanently removes the specified user from the project. This action cannot be undone and the user will lose all access immediately. Requires the `UpdateRolesAccountsAndGroups` permission.
  • get_userGet userGETReturns the complete user profile including portal role, content roles with access scope levels, and associated group memberships. Returns `404 Not Found` if the user does not exist in the project.
  • list_usersList usersGETReturns a paginated list of the project's team accounts. Their ids are the user_id that create, publish and fork tools need on API-key calls. Use search to filter by name or email.

Variable, 4 operations

  • create_variableCreate variablePOSTCreates a variable: a named value, global or per language, that articles can reference through its merge code. user_id is required with an API key.
  • delete_variableDelete variableDELETEPermanently removes the variable from the project. Articles that referenced the variable via its merge code will continue to contain the unresolved merge code until they are re-edited.
  • get_variableGet variableGETReturns the full variable representation including `dependency_article_count`. Returns `404` if the variable does not exist or belongs to a different project.
  • list_variablesList variablesGETReturns a paginated list of variable summaries. Dependency-article information is omitted from list responses to keep payloads small, use `get_variable` for `dependency_article_count`.

Attachment, 3 operations

  • add_article_attachmentAdd article attachmentPOSTAttaches a Document360 Drive file (supply `drive_file_id` and `media_folder_id`) or an external URL (supply `file_url` and `file_name`) to the article. Exactly one of `drive_file_id` or `file_url` must be provided.
  • delete_article_attachmentDelete article attachmentDELETERemoves the attachment with the given id from the article.
  • list_article_attachmentsList article attachmentsGETReturns the files attached to the article. For private or mixed-visibility projects, a time-limited SAS token is appended to Drive-hosted file URLs. Attachments are language-specific; pass `lang_code` to read attachments for a non-default language.

Bulk, 3 operations

  • bulk_create_articlesBulk create articlesPOSTCreates multiple articles in a single request. Each article is created independently; if one fails validation, the others are still created. The response includes per-article success/failure details. Maximum 100 articles per request.
  • bulk_create_categoriesBulk create categoriesPOSTCreates multiple categories in a single request. Each item in the request is processed independently, so individual categories may succeed or fail without affecting the others.
  • bulk_update_articlesBulk update articlesPATCHPerforms partial updates on multiple articles in a single request. Each article update is independent; if one fails, the others are still applied. Only fields included in each item are modified; omitted fields remain unchanged.

Mirrored, 3 operations

  • get_mirrored_articleGet mirrored articleGETReturns one mirror instance. `lang_code` defaults to the mirror workspace's default language; a mirror without that language returns 404. When `workspace_id` is supplied it must match the mirror's workspace.
  • list_mirrored_articlesList mirrored articlesGETReturns mirror instances in one workspace and language, optionally only those of one source article. `workspace_id` defaults to the project's main workspace and `lang_code` to that workspace's default language.
  • mirror_articleMirror articlePOSTCreates a read-only mirror of `source_id` in `category_id`. The mirror's workspace is the category's workspace; `workspace_id`, when sent, must match it.

Reader, 3 operations

  • create_readerCreate readerPOSTCreates a reader account and sends an invitation email to the given address. invited_by is required with an API key, which identifies no person. Part of the premium API add-on.
  • delete_readerDelete readerDELETEPermanently deletes the specified reader from the project. This action cannot be undone; once deleted, the reader must be re-invited to regain access. Requires the `UpdateRolesAccountsAndGroups` permission. Returns `204 No Content` on success.
  • list_readersList readersGETReturns a paginated list of readers for the specified project. Use the `search_email` query parameter to filter readers by email address.

Tag, 3 operations

  • create_tagCreate tagPOSTTag names are unique within the project, a name collision returns `409`. Tags can be created with or without a group.
  • get_tagGet tagGETReturns the tag with its dependency counts (articles, categories and files), its group and its creation details, the same values the Portal tag manager shows. The article and category counts include items in the recycle bin.
  • list_tagsList tagsGETReturns a paginated list of tags. Use `search` to match against the tag name (case-insensitive substring). List items do not include dependency counts, group or creation details: `dependency_*_count` is `0` and `group_*` / `created_*` are `null`.

Archive, 2 operations

  • archive_articleArchive articlePOSTArchives the specified language version: the article becomes read-only (every other write action on this language answers `409` until it is restored) and is excluded from publish/search surfaces.
  • archive_categoryArchive categoryPOSTArchives the specified language version: the category becomes read-only (every other write action on this language answers `409` until it is restored) and is excluded from publish/search surfaces.

Article template, 2 operations

  • get_article_templateGet article templateGETReturns the full article-template representation including the body content. `lang_code` scopes the lookup, supply the language the template was authored in.
  • list_article_templatesList article templatesGETReturns a paginated list of template summaries for the supplied language. The body (`content`) is omitted from list responses to keep payloads small, call `get_article_template` for the full body.

Content, 2 operations

  • bulk_update_category_contentBulk update category contentPATCHBatch-updates content for multiple categories in a single request. Each item is processed sequentially and the response contains per-item `success` results. Supports `auto_fork` per item to automatically create a draft if none exists.
  • get_category_contentGet category contentGETRetrieves the markdown or HTML body content of a category. For private or mixed-visibility projects, SAS tokens are appended to media URLs in the content by default.

Fork, 2 operations

  • fork_articleFork articlePOSTCreates a new draft version copied from an existing version, so edits can be made without affecting the live published version. Omit version_number to fork the currently published version; user_id is required with an API key.
  • fork_categoryFork categoryPOSTCreates a new draft version copied from an existing version of the category. The request body is optional: when omitted (or when `version_number` is null), the currently published version is forked.

Operation, 2 operations

  • get_operationGet operationGETReturns the status of a long-running background operation, such as the archive or unarchive of a category with children (their operation_id). queued and running are transient: call it again until a terminal status.
  • list_operationsList operationsGETReturns a paginated list of operations, newest first. Use `status` and `operation_type` to narrow the list, useful for reconciling in-flight work after a client restart without having stored every `Operation-Location`.

Project, 2 operations

  • get_projectGet projectGETReturns detailed information for a single project including its name, description, subdomain, and status. Returns `404` if the project does not exist or the user lacks access. Requires `ViewProjectSettings` permission.
  • list_projectsList projectsGETReturns the projects the API key can access, with pagination. Every other tool takes the project_id of one of them. Requires the ViewProjectSettings permission.

Setting, 2 operations

  • get_article_settingsGet article settingsGETReturns the SEO metadata, visibility flags, tags, status indicator, related articles, and custom field values (every active custom field of the project, with `null` values for unset fields) for the specified article.
  • get_category_settingsGet category settingsGETReturns SEO settings (title, description, slug), tags, visibility flags (exclude from search, AI search, external search), workflow status indicators, acknowledgement configuration, and custom field values.

Unpublish, 2 operations

  • bulk_unpublish_articlesBulk unpublish articlesPOSTUnpublishes up to 100 articles in a single request, reverting each to draft status. Each article is processed independently, if one fails, others are still unpublished. The response includes per-article success/failure results.
  • bulk_unpublish_categoriesBulk unpublish categoriesPOSTReverts multiple published categories back to draft status in a single request, up to a maximum of 100 per call. Requires `PublishArticles` permission. Each category is processed independently and the response contains per-item results.

Workspace, 2 operations

  • get_workspaceGet workspaceGETRetrieves a single workspace by its identifier. Returns a `404` response if the specified workspace does not exist within the project. Use `list_workspaces` to list all available workspaces and obtain valid identifiers.
  • list_workspacesList workspacesGETReturns a list of all workspaces within the specified project.

Api reference, 1 operation

  • list_workspace_api_referencesList workspace api referencesGETReturns a list of API reference definitions (OpenAPI/Swagger specifications) within the specified workspace. The response is currently unpaginated and returns all API references. Each entry includes the definition name and upload type.

Archived item, 1 operation

  • list_archived_itemsList archived itemsGETReturns one keyset page of archived articles and categories for the workspace + language, newest-archived first.

Copy, 1 operation

  • copy_drive_fileCopy drive filePOSTCreates a duplicate of the file in the specified destination folder. The original file in `folder_id` remains unchanged. The copy receives a new file ID. Requires `UpdateDrive` permission.

Custom field, 1 operation

  • list_custom_fieldsList custom fieldsGETReturns the custom field definitions configured for the project, including each field's type, options, and display metadata.

Default, 1 operation

  • get_default_drive_folderGet default drive folderGETReturns the folder configured as the default upload folder of the project's Drive (or, when none is configured, the first root-level folder): its id, title, subfolders and file count. Use get_drive_folder to list its files.

Document, 1 operation

  • get_document_by_urlGet document by urlGETLooks up an article or category by its relative URL path within the project. The `url` query parameter is required. Set `is_for_display` to `true` (the default) to receive rendered HTML content, or `false` for raw content.

Email availability, 1 operation

  • check_user_email_availabilityCheck user email availabilityGETReturns a boolean indicating whether the given email address can be used for a new user invitation. An email is considered unavailable if it already belongs to an existing user in the project.

Export, 1 operation

  • get_export_statusGet export statusGETReturns the current status of an export task previously created via `start_project_export`. When the task completes successfully, the response includes a `download_url`.

Import, 1 operation

  • get_import_statusGet import statusGETReturns the current status of an import task previously created via `start_project_import`. Returns `404` if the import ID is invalid or does not belong to the specified project. Requires `ViewProjectSettings` permission.

Keyword, 1 operation

  • list_top_search_keywordsList top search keywordsGETReturns a paginated list of keywords ranked by search frequency. Each keyword includes the search count, viewed count, read count, and bounced count. Use this to identify what users are searching for most. Requires `ViewAnalytics` permission.

Language, 1 operation

  • list_workspace_languagesList workspace languagesGETReturns the list of languages configured for the specified workspace. If `workspace_id` is omitted, languages for the default workspace are returned. Returns an empty list when no languages have been configured.

Me, 1 operation

  • get_current_userGet current userGETReturns the full profile of the user identified by the current authentication token, including their portal role, content roles with access scope levels, and group memberships.

Most read, 1 operation

  • list_most_read_articlesList most read articlesGETReturns the top 5 articles ranked by total read duration (time spent reading). This highlights content that users spend the most time engaging with, which may differ from the most-viewed articles.

Most referenced article, 1 operation

  • list_ai_search_most_referenced_articlesList ai search most referenced articlesGETReturns a list of articles ranked by how often they are cited as sources in AI-generated answers. Use this to understand which articles are most relied upon by the AI search engine.

No result, 1 operation

  • list_no_result_search_keywordsList no result search keywordsGETReturns a paginated list of keywords that produced zero search results. Use this to identify content gaps, these are topics readers are searching for but cannot find in the knowledge base.

Query, 1 operation

  • ai_search_queryAi search queryPOSTSends a natural language query to the AI assistive search engine and returns a generated answer based on the project's documentation content.

Role, 1 operation

  • list_user_rolesList user rolesGETReturns both system-defined and custom roles for the project. Each role includes its type (portal or content) and whether it is a built-in system role.

Sso scheme, 1 operation

  • list_sso_schemesList sso schemesGETReturns SSO authentication schemes configured for the project with pagination support, including each scheme's name and display name. If SSO has not been configured, an empty list is returned rather than an error.

Task, 1 operation

  • get_drive_task_statusGet drive task statusGETChecks the current status of an asynchronous background task such as a bulk upload. Task IDs are returned from async operations like file uploads. Poll this endpoint to determine when the task completes. Requires `ViewDrive` permission.

Top, 1 operation

  • list_top_articlesList top articlesGETReturns a paginated list of articles ranked by engagement metrics such as views, reads, likes, and dislikes. Supports sorting by any metric column and ordering. Use this endpoint to identify the highest-performing content in the project.

Top category, 1 operation

  • list_top_categoriesList top categoriesGETReturns a paginated list of categories ranked by aggregate engagement metrics across all articles within each category. Supports sorting and ordering. Requires `ViewAnalytics` permission.

Translation, 1 operation

  • list_articles_by_translation_statusList articles by translation statusGETLists articles filtered by their translation status for the given language code. Valid status values are `none`, `needTranslation`, `translated`, and `inProgress`. Requires the `ViewArticles` permission.

Trending topic, 1 operation

  • list_ai_search_trending_topicsList ai search trending topicsGETReturns AI-identified topic clusters from search queries, ranked by question count. Topics with `is_no_search_cluster` set to `true` represent clusters of unanswered queries, these highlight content gaps.

Workflow status, 1 operation

  • list_workflow_statusesList workflow statusesGETReturns workflow statuses configured for the project with pagination support. If no workflow has been set up, an empty list is returned rather than an error. Each status includes its name, description, and whether it is read-only.

Showing the first 120 of 154 endpoints. The rest are in the product, searchable from the workflow builder and from chat.

Use Document360 from Claude Code, Cursor or Codex

Connect Document360 in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Document360 operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Document360

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Document360 once

    Add your Document360 connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Document360 integration FAQ

What can you do with the Document360 integration?

LiveContext exposes 154 operations on Document360, covering article, group, version and label.

Popular integrations

Browse the whole catalog