1. Bring your own MCP client
What it is — The Atomicwork MCP Server lets you connect Atomicwork to any MCP-compliant client and build on our APIs.
Why it matters — MCP is becoming the standard way AI tools connect to external platforms. This means you're not limited to the Atomicwork interface to get things done.
You can ask your AI assistant, like Claude for instance, to pull up your open tickets, summarize what's pending, or even mark a completed request as resolved, all without switching tools.

How it works — Head over to the MCP documentation here to get started.
2. Sign in with JumpCloud SSO
What it is — Atomicwork now supports SAML 2.0 single sign-on with JumpCloud. Your team signs in with their existing JumpCloud credentials – no separate Atomicwork password – and access is managed through JumpCloud groups.
Why it matters — One less password to manage, one less place credentials can leak, and access control that lives where your identity policies already do.
How it works — Admins can set it up in Settings → Security → JumpCloud SSO. Note that only one SSO provider can be active per tenant at a time.
3. A cleaner way to compose
What it is — A revamped composer across Request, Service Request, Incident, Change, and Problem detail pages – cleaner, denser, and faster to compose.
Why it matters — The old composer's fixed toolbar and stacked attachments ate up space and slowed you down mid-reply. This redesign clears that clutter without losing any functionality.
What's changed —