Skip to main content
Glama
Sign In
DA Admin MCP Server

DA Admin MCP Server

by kptdobe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

DA Admin MCP Server

An MCP (Model Context Protocol) server that provides tools for interacting with the Document Authoring Admin API. This server allows you to manage content, versions, and configurations in DA repositories through MCP tools.

Features

  • List sources and directories in DA repositories

  • Manage source content (get, create, delete)

  • Handle content versioning

  • Copy and move content between locations

  • Manage configurations

  • Lookup Media and Fragment References

Related MCP server: mcp-docmost

Cursor AI setup

To use this MCP server with Cursor AI, go to Cursor Settings, MCP and a New global MCP server. Add this entry to your list of mcpServers:

"da-live-admin": {
 "command": "npx",
  "args": [
    "https://github.com/kptdobe/mcp-da-live-admin"
  ],
  "env": {
    "DA_ADMIN_API_TOKEN": "your_api_token_here"
  }
}

In the chat, you can then ask things like: Via the DA Admin, give me the list of resources in <your_org>/<your_repo>/<path>.

Contributing

  1. Fork the repository

  2. Create your feature branch

  3. Commit your changes

  4. Push to the branch

  5. Create a new Pull Request

License

MIT

Available Tools

10 tools
da_admin_create_sourceA

Create source content within an organization: can be an html file or a json file

Inputs: ext (required), org (required), path (required), repo (required), +1 more.

da_admin_delete_sourceB

Delete source content from an organization: can be an html file or a json file

Inputs: ext (required), org (required), path (required), repo (required).

da_admin_get_sourceC

Get source content from an organization: can be an html file or a json file

Inputs: ext (required), org (required), path (required), repo (required).

da_admin_list_sourcesB

Returns a list of sources inside a folder from an organization

Inputs: org (required), path (required), repo (required).

da_media_check_statusA

Check if media index exists on a site. Returns initialization URL if not found.

Inputs: org (required), repo (required), path.

da_media_find_usageB

Find all documents using a specific media item by URL or name.

Inputs: org (required), repo (required), path, mediaUrl, +1 more.

da_media_get_indexB

Get the complete media index (media.json) for a site. Returns all media references with timestamp.

Inputs: org (required), repo (required), path.

da_media_get_statsA

Get media usage statistics including total count, breakdown by type, unused media count, and alt text status (filled/decorative/notFilled).

Inputs: org (required), repo (required), path.

da_media_refresh_cacheA

Refresh the media data cache by fetching the latest media.json. Use when media has been updated.

Inputs: org (required), repo (required), path.

da_media_searchC

Search and filter media items by type, document, name, alt text, unused status, or missing alt text.

Inputs: org (required), repo (required), alt, doc, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Tools are clearly separated into two groups (da_admin for sources and da_media for media) with distinct actions. Within each group, no two tools have overlapping purposes; each performs a unique operation.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with prefixes 'da_admin_' and 'da_media_'. Verbs are action-oriented (list, get, create, delete, check, refresh, get, search, find), creating a predictable naming scheme.

    Tool Count5/5

    10 tools is well-scoped for the domain covering source management and media metadata operations. Each tool serves a distinct purpose without unnecessary bloat or gaps.

    Completeness4/5

    Source tools cover list, get, create, delete, but lack an update operation. Media tools provide comprehensive operations for checking, refreshing, searching, and analyzing media, but no create or delete for media items (assuming they are managed via sources). Minor gap in source update.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers