Skip to main content

MCP Server

Dotwork's customer-facing MCP server lets users connect to Dotwork through SSO and safely use Dotwork tools for querying artifacts, fields, relationships, and the operating ontology.
​

Use the MCP endpoint for your environment:

https://<your-dotwork-subdomain>.dotwork.app/ai/mcp

Dotwork's MCP Server is in Beta and AI can make mistakes. Always make sure you verify answers and actions.
​

What It Can Do

  • Read workspace context

  • Query Dotwork data

  • Write Dotwork data

  • Run Dotwork agent workflows

The server acts with the authenticated user's Dotwork permissions and active site context.
​

Authentication

Dotwork uses the normal sign-in flow for MCP:

  1. The MCP client connects to Dotwork.

  2. Dotwork opens sign-in.

  3. The user authenticates with SAML SSO, OAuth, or basic auth.

  4. Dotwork redirects back to the MCP client callback.

  5. Tool calls run with that user's Dotwork identity and site policy.

For local or automation-only environments, a bearer token can be supplied by config, but SSO/OAuth is preferred for customer-facing use.
​

Cursor

Configure the Dotwork MCP manually in .cursor/mcp.json or ~/.cursor/mcp.json:
​

{
  "mcpServers": {
    "dotwork": {
      "url": "https://<your-dotwork-subdomain>.dotwork.app/ai/mcp"
    }
  }
}

Then restart Cursor and check Settings → Tools & MCP. Complete SSO when prompted by 'Needs Authentication'.

Clicking connect will trigger the auth flow in Dotwork
​

Claude Code

Add the remote HTTP server:

claude mcp add --transport http dotwork https://<your-dotwork-subdomain>.dotwork.app/ai/mcp

Then run:

/mcp

Codex

Add Dotwork to ~/.codex/config.toml or a trusted project .codex/config.toml:

[mcp_servers.dotwork] url = "https://<your-dotwork-subdomain>.dotwork.app/ai/mcp"

Use /mcp in the Codex TUI to verify. If OAuth login is supported for the endpoint:

codex mcp login dotwork

ChatGPT

ChatGPT connectors require a public HTTPS MCP endpoint. In most environments, you will have to turn on developer mode in order to set up and use the Dotwork MCP initially before publishing for your workspace.
​

  1. Enable developer mode in Settings → Apps & Connectors → Advanced settings.

  2. Go to Settings → Connectors → Create.

  3. Name the connector Dotwork.

  4. Set the connector URL to https://<your-dotwork-subdomain>.dotwork.app/ai/mcp.

  5. Create the connector and confirm the tool list appears.

  6. In a new chat, use + → More → Dotwork.

Write tools require confirmation unless the user chooses to remember approvals.

Verify

Ask the client:

Use Dotwork MCP to get my current environment context and list the site spaces.

Expected tools:

  1. environment_get_context

  2. site_get_from_context

  3. site_get_spaces

  4. site_get_ontology

Then try:

List artifact kinds in this Dotwork site and show the first page of artifacts for one kind.

Expected tools:

  1. artifact_get_kinds

  2. site_get_spaces

  3. space_get_artifact_kind_contexts

  4. query_artifacts or artifact_get_by_kind

Troubleshooting

Issue

Fix

Server does not appear

Restart the client and reload MCP settings.

SSO does not return to client

Confirm the MCP endpoint and callback belong to the same environment.

Tool list is empty

Re-authenticate and check site MCP policy.

401 or unauthenticated

Re-run the MCP auth flow.

Missing site or space

Call environment_get_context, site_get_from_context, and site_get_spaces; pass explicit ids if needed.

Query returns no artifacts

Re-resolve the Space and ArtifactKindContext before calling query_artifacts.

Field update fails

Call field_get_available and field_get_details before field_update_value.

Did this answer your question?