Your MCP server, under your domain.

Access: each person’s authorized context

Your team keeps a familiar conversational interface. The OS configured for your company brings the authorized context and workflows.

Your collaborators ask about customers, appointments, messages, missions or calls without learning internal tool names.

Your work OS supplies only the information the current person and workspace are allowed to use.

Important actions remain behind a clear preview and the expected human confirmation.

Your collaborators do not need to learn another generic application before asking a useful question. They can use ChatGPT or another compatible assistant and speak about the work in normal language.

The OS configured for your company supplies the customer, appointment, message, mission, product or call context that the current user is allowed to access.

Every connection is scoped to an authenticated person and an authorized workspace. The application does not expose a raw database and does not give every employee the same visibility.

Missing or unauthorized information must remain unavailable rather than being guessed.

AlefOS public discovery describes the product. A company’s public services expose only the operations and information it chooses to publish. Identified private access permits operations authorized for the person’s role and relationship; these are three separate scopes.

Connection: from your assistant to your work OS

Your MCP access can be configured under your domain, for example ai.yourcompany.com. Your team adds the configured connection to a compatible assistant and completes the required sign-in flow. The server checks permissions before returning data or executing an operation. A domain name grants no additional access and does not mean ChatGPT is hosted by your company.

It lets a compatible assistant communicate with your company work OS. Identity, workspace and permissions are checked before context is returned.

Receives the natural-language request from the current user.

Provides only the authorized business context and supported workflow.

Applies the access and execution rules that support your work.

MCP is the secure connection between the assistant and your company work OS.

It exposes discoverable tools, structured inputs and explicit results. The useful experience is simple: ask a business question, receive an answer grounded in authorized company context, then review any important action before it happens.

Everyday questions and workflows

The user simply talks to the assistant. The company work OS brings the context it is allowed to use.

Which customers still need a response?

What should I know before tomorrow’s appointments?

What did this customer ask for in the last exchange?

Prepare the next follow-up for review.

Customer follow-up: “Which objection remains open before my callback?” Manager: “Which intervention still needs a decision from my team?” Meeting: “What commitment was recorded and who prepares the next step?” Answers depend on accessible context; missing information remains missing.

For customers: “Find an apartment near the station,” “I would like a boiler service,” “Find the manual for my installation.” Your plugin checks published offers or the authorized customer file, then prepares the configured next step. A submitted request becomes a booking only after the relevant service confirms it.

Actions: read, prepare and execute

Your work OS can prepare useful work, but actions that affect customers, calendars, groups or company records stay controlled.

Operating rule

A clear proposal. A controlled decision.

The company work OS can prepare a follow-up, appointment, mission, message or briefing when that workflow has been configured.

The sequence remains: request, clear preview, confirmation and traceable execution. Execution follows the authorization and confirmation policy of the specific tool.

Interfaces: in the conversation and on the web

When a compatible ChatGPT interface has actually been delivered for the workflow, the conversation can display a useful view such as a customer card, appointment preview or approval step.

This is not promised identically in every assistant. The available interface depends on the configured work environment and supported client.

AlefOS connects context, access, compatible services and authorized actions.

The people using the deployed solution work with the company work OS, its name and its workflows. The reference below documents the available tools and access boundaries for configuration and technical review.

Compatibility: check the client and workflow

ChatGPT and Claude endpoints are documented. Authentication, enabled modules and client capabilities determine the available workflow. Grok and other clients must be checked against their current connection flow.

An MCP connection does not guarantee an embedded visual interface in every assistant. Distinguish a tool call, a displayed result and an interactive interface actually delivered.