MindscapeAI workspace · Core and Cloud
Core and Cloud
Decide what to do and what data to use in one place. At the production or delivery step, send the work to the tool and environment it needs.
How a task runs
Core manages project context, available tools, tasks, and records in the workspace. For a local publication, editors decide in the workspace which draft and references to use and when review is needed.
MindscapeAI Cloud offers managed capabilities that work with the workspace. Teams can also connect external services for individual steps, such as drafting on an authorized site or handing an image task to a configured runtime.
The tools, models, and settings you choose determine which data leaves the workspace and whether you can work offline. If you use your own key or another external model, data needed for processing goes to the provider according to your configuration. Teams can check the data and services each step uses.
- Organize tasks and reference material in the workspace
- Check available tools, data, and permissions
- Run the work in a suitable environment
- Review results and sources in the workspace
Ways to connect
- Plugin · Add a capability
- Bring new functionality into the workspace. A plugin can provide tools, workflows, or controls. After connection, workspace settings determine which tasks can use it.
- MCP · A shared way to connect tools
- A protocol for connecting tools. Supported clients can discover or call permitted tools on compatible services. Available tools depend on the service and permissions.
- Adapter · Connect a specific service
- Send workspace requests to a specific system using its own interface and bring the results back so the team can track them in the workspace.
- Runtime · Where the work runs
- An environment that runs a model, tool, or production step, such as a local process or configured remote service. Different tasks can have different environment, account, and resource requirements.
Example of preparing a feature for publication
An editor adds approved text and images to a delivery task. If the workspace is connected to the right content service, the task can send the selected version as configured, create a draft, and return the result for the team to review. Publication follows the established review and authorization process.