DUMA/ API

Your workspace, connected to AI.

The DUMA MCP server lets your assistant work with products, content, media and notes. Connect your client once, then ask for what you need in plain language.

Create a workspace key Browse 88 tools

88 toolsStreamable HTTPWorkspace API keys

Connect in three steps

  1. Step 1: Create a workspace key

    Start with a publishable key and catalog:read or content:read to explore your data. For drafting or management, use a secret key with the specific scopes you need.

    Open Settings → Developers

  2. Step 2: Add DUMA to your client

    Run this in your project’s terminal. Replace YOUR_API_KEY with your workspace key.

    Terminal
    claude mcp add --transport http duma https://api.duma-business.com/v1/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

    Open Claude Code and run /mcp to check the connection.

    Claude Code connection guide ↗

    Keep secret keys in your local client configuration. Do not commit them to a repository or paste them into an assistant conversation.

  3. Step 3: Check the connection

    Ask your assistant to call workspace_info. It returns the key’s scopes, restrictions and available APIs.

    Prompt
    Use DUMA’s workspace_info tool and summarize which APIs and permissions this connection has. Don’t change any data.
    Works with any valid workspace key

You choose what the assistant can do

Scopes

Access follows your key

Tool discovery is filtered by scope. Calls also check enabled modules, resource restrictions and, for management tools, the key creator’s current permissions. Notes follow that person’s folder access.
View all API key scopes
Audit log

Draft, publish and delete are separate

Creating a content entry saves a draft. Publishing needs content:publish; deleting content needs content:delete. Management changes are recorded in the workspace audit log.

Find a tool

Filter by name, scope and action. Your assistant only receives the tools allowed by its key; linked tools open their API reference.

88 tools in 7 areas

Content32
Store6
  • store_list_productscatalog:readread
  • store_get_productcatalog:readread
  • store_list_categoriescatalog:readread
  • store_list_localescatalog:readread
  • store_get_orderorders:writeread
  • store_quote_orderorders:writeread
Media7
Notes14
Catalogue15
Locations3
Workspace11

Connection help

The server rejects my key

Replace the placeholder with a valid workspace key and check that it has not expired or been revoked. Send it in the Authorization: Bearer header, or X-Api-Key. Legacy dcms_ content keys are not accepted.

A tool is missing or access is denied

Check the key’s scopes first, then refresh the client’s tool list. A listed tool may still be denied by module settings, content-type restrictions or the key creator’s current access. Workspace-wide management also requires an unrestricted workspace key and owner access.

Opening the server URL gives 405

This is expected for a browser GET request. Connect through an MCP client using Streamable HTTP. DUMA accepts JSON-RPC over POST; GET and DELETE return 405 because the server is stateless.

A request is rate-limited

The MCP endpoint allows 120 requests per minute per key. A 429 response means the limit was reached. Wait before retrying and reduce request frequency; the underlying APIs also enforce their limits.

How do media uploads work?

The remote server cannot read a file path on your computer. Import a public HTTPS image URL or send a small file as base64. MCP requests are capped at 1 MB; use the authenticated multipart upload URLs returned by workspace_info for larger files, up to 25 MB.