Obelism
One account, one Organization and one MCP server for Improve, Content, Numbers and Media. How Organizations, roles, Spaces and agents work across every product.
Obelism makes the tools around a website or an online shop: Improve for A/B tests and feature flags, Content for content, Numbers for analytics and Media for files. Each product has its own docs. These docs are about what they share, managed on www.obelism.studio: your account, your Organization and its people, the Spaces your sites live in, and the MCP server that gives an agent every product at once.
How it fits together
Organization members, roles, product access, billing
└── Space one site or project, shared by every product
├── develop ┐
├── staging ├ Improve's tests, Content's entries, Numbers' events
└── production ┘- An Organization is your company or a client: its members, what each may do, and its billing. You can belong to several and switch between them in any product.
- A Space is one site or project in it. Every product works in Spaces, so a site's tests, pages, files and numbers are in the same one.
- An environment is a copy of a Space's data in Improve, Content and Numbers:
develop,stagingandproduction.
In these docs
- How the products work together: what each product reads from or sends to another.
- Organizations: creating one, inviting people, switching and deleting.
- Roles: admin, developer, editor and reader, and what each may do in every product.
- Product access: keeping a member out of a product, or a Space, or switching a product off.
- Spaces: environments, allowed origins, connected deployments, Shopify, transferring and deleting.
- Your account: passkeys, two-factor authentication, sessions and connected apps.
- Agents: the MCP server for every product, the Claude plugin and ⌘K.
- What an agent may do: scopes, roles and production, per product.
For agents
Every page here is also Markdown: add .md to its URL. llms.txt lists every product's docs, and llms-full.txt has them all in one file.