- Home
- MCP servers
- DA Live Admin
DA Live Admin
- typescript
0
GitHub Stars
typescript
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You can run a remote MCP server that exposes the DA Live Admin API to your AI assistants. This server lets Claude or similar agents manage DA repositories through a secure, edge‑deployed MCP endpoint with token passthrough and health checks, enabling streamlined repository operations from your AI workflows.
How to use
Set up your MCP client to connect to the DA Live Admin MCP server using an authorized connection. You will pass the DA Admin API token in the Authorization header so the server can forward requests securely to the DA Admin API. Once connected, you can request operations like listing sources, reading or updating files, changing repository config, and inspecting media or fragment references. All actions happen through the MCP endpoint, enabling your AI assistant to perform repository tasks with natural language prompts.
How to install
Prerequisites: you need Node.js 18+ and npm. You also require a Cloudflare account (free tier works) and the Wrangler CLI installed.
Step 1: Install Wrangler globally if you haven’t already.
Step 2: Clone the project, install dependencies, and start the development server locally.
Step 3: Deploy to Cloudflare Workers once you are ready to publish.
Configuration and usage notes
Health checks expose the server status at /health. The MCP endpoint is at /mcp. Authentication is done by passing your DA Admin API token in the Authorization header when you connect from your MCP client. The Worker URL after deployment will look like your‑account.workers.dev, and you should include /mcp in the URL.
Example connection setup details you will configure in your MCP client (example URL shown): the HTTP endpoint is https://mcp-da-admin.your-account.workers.dev/mcp and you pass the token in the Authorization header as a Bearer token.
Security and reliability
Tokens are passed through without being logged or stored by the MCP server. All communication uses HTTPS. Input validation, CORS handling, and health checks are in place to provide secure, reliable operation.
Troubleshooting
If you encounter a missing token error, verify that your MCP client configuration includes the Authorization header with your DA Admin API token. For timeouts, the default ceiling is 30 seconds; large operations may require more time on the DA Admin API side or optimization of the request.
Available tools
da_list_sources
List sources and directories in a repository
da_get_source
Get content of a specific source file
da_create_source
Create a new source file
da_update_source
Update an existing source file
da_delete_source
Delete a source file
da_copy_content
Copy content between locations
da_move_content
Move content between locations
da_get_versions
Get version history for a file
da_get_config
Get repository configuration
da_update_config
Update repository configuration
da_lookup_media
Lookup media references
da_lookup_fragment
Lookup fragment references