AtriumKit

com.atriumkitPublished by atriumkit.comOfficial publisherv1.0.0Updated Nov 1, 2026

Edit, translate, narrate, publish and analyze AtriumKit interactive demos from any MCP client.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Data & Analytics Media & Design

Server details

Identifier: com.atriumkit/atriumkit
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Nov 1, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to atriumkit.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.atriumkit%2Fatriumkit.svg)](https://sourceweft.com/mcp/com.atriumkit%2Fatriumkit?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted AtriumKit MCP server that lets an assistant edit, translate, narrate, publish and analyze interactive product demos.

What you can do: List and read demos, collections, screens and published guides
Edit steps, copy, settings and translations, duplicate demos and add them to collections
Rewrite copy with AI, translate, generate voiceovers and create personalized links
Publish and unpublish demos
Read analytics such as views, completion rates, step funnels and traffic sources, plus lead form data
Search the workspace knowledge base
When to use it: Useful when your product demos, guides and videos live in AtriumKit and you want an assistant to rewrite or translate copy, add voiceovers, publish changes, or answer questions about viewer drop-off and leads without opening the app.
Requirements: Remote Streamable HTTP endpoint at app.atriumkit.com/mcp; nothing to install. OAuth 2.1 sign-in and approval in the browser, or a personal access token sent as an Authorization Bearer header. Works on every AtriumKit plan; some features need Pro or Team and AI credits.

Before you install

The assistant can change demos, publish or unpublish them, and read analytics and lead data (names, emails, companies) if that scope is granted. Grant only the scopes you need; workspace role still limits what is possible. Changes appear in version history and can be restored. Tokens work only on the MCP server and can be revoked; each connection is limited to one workspace.

Installation

In SourceWeft

Open AtriumKit in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.atriumkit%2Fatriumkit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "atriumkit": {
      "type": "http",
      "url": "https://app.atriumkit.com/mcp"
    }
  }
}

README

AtriumKit MCP server

AtriumKit makes interactive product demos, step-by-step guides and videos from one recording. Its hosted MCP server lets an AI assistant work on your demos for you: "rewrite the tooltips for a CFO", "translate it into German and publish", "which step loses the most viewers?".

This repository is documentation only. The server is hosted by AtriumKit, so there is nothing to install or run.


Server URL	`https://app.atriumkit.com/mcp`
Transport	Streamable HTTP
Auth	OAuth 2.1 (sign in and approve in the browser), or a personal access token sent as `Authorization: Bearer <token>`
Plans	Every AtriumKit plan
Clients	Claude (claude.ai, Desktop, mobile), Claude Code, ChatGPT, Cursor and other MCP clients

Full setup guide with screenshots: Connect Claude, ChatGPT or Cursor to AtriumKit.

Connect

Claude

Works in claude.ai, Claude Desktop and the Claude mobile apps.

Open Customize → Connectors and choose Add custom connector. On Claude Team and Enterprise, an Owner adds it under Organization settings → Connectors, then each member clicks Connect.
Paste https://app.atriumkit.com/mcp. Leave the OAuth client fields empty.
Click Add, then Connect.
On the AtriumKit page that opens, sign in, pick the workspace and what Claude may do, then click Allow access.

Claude Code

Then run /mcp in Claude Code, pick atriumkit and choose Authenticate.

ChatGPT

Custom MCP servers need developer mode, which is available on some ChatGPT plans.

In ChatGPT settings, open Apps → Advanced settings and turn on Developer mode.
Add a custom MCP server named AtriumKit, paste the server URL and choose OAuth. Leave the client ID and secret empty.
Sign in to AtriumKit, pick the workspace and what ChatGPT may do, then click Allow access.

Cursor

Add this to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project). Cursor asks you to sign in the first time it connects.

Other clients

Point any MCP client that supports Streamable HTTP at https://app.atriumkit.com/mcp. Clients that support OAuth discover the authorization server from https://app.atriumkit.com/.well-known/oauth-protected-resource/mcp. For a client or script that can only send a fixed token, create a personal access token in AtriumKit under Settings → AI assistants & MCP → Access tokens and send it as Authorization: Bearer <token>. Tokens work only on the MCP server, never to sign in, and AtriumKit emails you when one is created.

Permissions

You choose these when you connect an app or create a token. Your workspace role still applies: a viewer's assistant can't edit, whatever was ticked.

Scope	Name	What it allows	Role needed
`demos:read`	Read demos	See demos and collections: steps, copy, screens, share settings and links. Always included	Viewer
`demos:write`	Edit drafts	Change steps, copy, settings and translations, duplicate demos and add them to collections	Editor
`demos:publish`	Publish	Publish and unpublish demos	Editor
`analytics:read`	Read analytics	Views, completion rates, step funnels and traffic sources	Viewer
`leads:read`	Read leads	Names, emails and companies from lead forms. Only when you tick it	Viewer

What an assistant can do

List and read demos and screens; edit copy and steps; add choices; link navigation in clickable demos; rewrite copy with AI; translate; generate voiceovers; publish and unpublish; read analytics and leads; create personalized links; add demos to collections; read published guides; and search the knowledge base.

Plan limits apply as in the app: translations, voiceovers, personalized links and the knowledge base need Pro or Team, and AI rewrites and translations use the workspace's AI credits.

Every change an assistant makes shows in the demo's version history, marked like "Edits by Ana (via Claude)", and can be restored. Assistants see screens the way viewers do: blurred areas, redacted text and personal data on screenshots never go out.

Limits

Each connection or token works in one workspace. Connect again to use another.
Up to 120 requests a minute per connection or token.
Up to 25 active tokens per workspace.

Disconnect

In AtriumKit, open Settings → AI assistants & MCP and click Disconnect next to an app or Revoke next to a token. It stops working right away.

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestNov 1, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.