Dawiso supports the Model Context Protocol (MCP), which enables AI and LLM tools to interact with your Dawiso environment. Through MCP, external tools can look up information or carry out actions directly in Dawiso, making it easier to retrieve context or automate bulk operations.
By combining Dawiso with LLM capabilities, organizations can enrich AI tools with trusted metadata, boost the productivity of data stewards and other data users, and even enable internal agents that work directly with governed data.
To configure Dawiso MCP for e.g., Claude or Cursor, see AI agentic tools: Example settings.
To enable Dawiso MCP, it must first be activated for your customer environment. Please contact our Sales or your Customer Success Account Manager for assistance.
MCP is currently available for cloud customers. For on-premises deployments, contact your Customer Success Account Manager for details on support and version compatibility.
Categories of MCP tools
Each MCP tool covers one domain, such as objects, search, permissions, or translations, and is strictly read-only or read-write, never both. Tools fall into two categories:
1. Retrieve information
Use MCP to retrieve data from Dawiso without making changes. Typical capabilities include:
- Search for objects by name, full text, or labels, or run a semantic search over your catalog when Ask Dawiso AI is enabled.
- Trace data lineage from a selected object, find upstream or downstream dependencies.
- Retrieve system information on available spaces, applications, object types, and relation types.
- Preview objects access details such as attributes, workflow states, concepts, attachments, user-object relations, or graph-specific metadata.
- Preview an object’s data sample by retrieving its columns and rows.
- View user and user group details, or list local users.
2. Carry out commands and actions
Use MCP to perform operations directly in Dawiso, especially useful for bulk tasks. Supported actions include:
- Comprehensive object management:
- Object lifecycle: Create or delete objects, bulk publish concepts, and update their workflow states.
- Attributes and metadata: Update attributes, manage files, or change workflow states.
- Facilitate collaboration: Add comments and labels, including area and classifications such as PII or GDPR.
- Upload data samples: Attach a CSV or JSON data sample to an object. Uploading a new sample replaces the object’s existing sample.
- Manage permissions: Grant or retrieve permissions to users on object or space level.
- Manage local users and group memberships: Create, edit, or delete local Dawiso users, reset their passwords, or update group memberships. Available only for in-memory auth. On deployments using SSO (Azure, LDAP, OIDC), users are synced from the identity provider and can’t be managed through MCP.
- Space and application management: Create, update, or delete spaces and applications. List available icons and workflow states.
- Bulk translation: Create translations for up to 500 objects in a single call using
create_translations_batch.
Dawiso MCP can be configured in read-only mode or with full write access, depending on your needs. For more information, see AI agentic tools: Example settings.
Example use cases
| Use case | Category | Description |
|---|---|---|
| Find and classify objects | Look up & classify objects | Search for all objects with “customer” or “client” in their name, then add a PII label and assign GDPR classification. |
| Bulk object creation | Object management (bulk) | Mass-create new Business Glossary objects in Dawiso from a predefined list, automatically generate descriptions for them, and set their workflow state to Review. |
| Enrich and classify with AI | Metadata management & AI integration | Update object attributes, automatically classify and label objects (e.g., PII, GDPR), and provide Dawiso metadata to internal agents such as chatbots or developer tools. |
Tool visibility by role
tools/list returns only the tools available to the connecting user’s effective role, so a Viewer, a Contributor, and an Admin see different tool sets from the same MCP connection.
| Role | What’s available |
|---|---|
| Viewer | Read tools only: search, retrieve, and preview. |
| Contributor | Read tools, plus write tools for objects, comments, attachments, and workflow states. Demoted to Viewer’s read-only set when your environment has the contributor read-only restriction mode enabled. |
| Admin | The full tool surface, including space, permission, and package administration. |
The MCP tool surface was rebuilt into smaller, single-purpose tools, replacing the previous set of broader, multi-action tools. If you configured an AI agent against the old tool names, reconnect it and let it re-fetch tools/list to pick up the new names.
Tool responses
Every tool shares one response envelope, and tool descriptions carry their parameters directly in the schema instead of a longer free-text explanation, so an agent can tell what a tool needs and returns without a separate lookup.
A tool that lists or searches for records pages its results at 20 items by default, capped at 100 per call. Two parameters narrow what comes back:
mode: controls how much detail each result carries, from a minimal summary to the full record.fields: selects which fields to include, instead of returning every field a result normally carries.
Access restrictions
Single sign-on (SSO)
SSO does not limit MCP access by itself. MCP uses the same Dawiso API endpoint and authentication as your users. If that endpoint is publicly reachable, agents can connect from any network as long as they have valid credentials, even when SSO is enabled.
IP Whitelisting
When network access is restricted by IP allow-listing, MCP connections are supported starting in Dawiso 2025.11.
Contact your Account Manager to enable IP whitelisting and provide the source IPs/CIDRs to permit.
Managing tool access
Administrators manage an environment-wide MCP tool allowlist, and each user can narrow their own available tools further. See MCP Tools Management for the settings pages and full walkthrough.