> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Apps and connections

> Select an application, check access and recover connections.

<h2 id="select-an-app">
  1\. Select an app
</h2>

<span id="select-an-app-overview" />

No apps is a valid standalone context. To work in another application, select its connected instance and intended document.

Select the application that holds the material you want to work on: a Revit project or family, an AutoCAD drawing, a Rhino model or a Blender scene.

<span id="select-an-app-in-ideatura" />

1. Choose standalone work or the intended TargetApp.
2. Check application name, document and connection state.
3. Confirm the required access level.
4. Run a small task appropriate to that application.

<span id="select-an-app-check-the-result" />

The task is directed at the correct environment.

<h2 id="access-levels">
  2\. Access levels
</h2>

<span id="access-levels-overview" />

The connected-app selector offers access levels such as Read, Markup and Full. Read the options available for the selected application and choose the access needed for the task.

An IFC viewer’s Read only label describes that viewed file. TargetApp access describes what Ideatura may do in a connected application. They must not be treated as the same switch.

<span id="access-levels-in-ideatura" />

1. Inspect the target’s access selector.
2. Choose the level needed for the task.
3. Confirm the selected document.
4. Check what operations are available.

<span id="access-levels-check-the-result" />

Both the target application and viewed file have the intended access state.

<h2 id="execution-modes">
  3\. Execution modes
</h2>

<span id="execution-modes-overview" />

Core, Advanced and Direct are execution modes. Read the selected mode’s description and any access warning before running work in a connected application.

Mode is separate from the AI model and the target permissions. Check the selected document and the access it requires before enabling Direct.

<span id="execution-modes-in-ideatura" />

1. Identify the active agent route and target.
2. Read the mode description.
3. Select the required mode and review any access transition.
4. Test a bounded operation and inspect the result.

<span id="execution-modes-check-the-result" />

You know which execution surface is being used and what access it requires.

<h2 id="mcp-connections">
  4\. MCP connections
</h2>

<span id="mcp-connections-overview" />

MCP is a way for an AI application to access tools and context from connected services. In Ideatura it has a named Settings tab.

Before using a connection, check which account it uses, which tools it exposes and which actions those tools can perform. An available connection does not guarantee access to every tool.

<span id="mcp-connections-in-ideatura" />

1. Open Settings → MCP.
2. Inspect the configured connections and their status.
3. Identify the tools or resources relevant to the task.
4. Test a clearly scoped operation.

<span id="mcp-connections-check-the-result" />

You can identify the connected service and the intended operation.

<h2 id="recover-connections">
  5\. Recover connections
</h2>

<span id="recover-connections-overview" />

When a target or service is unavailable, first identify which connection failed: AI route, MCP service or native application. Read the error and check its current state before retrying.

For a native application, confirm the app is running and the intended document is open. After reconnecting, recheck both the target and access level.

<span id="recover-connections-in-ideatura" />

1. Identify the failed connection and error.
2. Check the prerequisite application, account or document.
3. Reconnect through the appropriate control.
4. Run a small verification task.

<span id="recover-connections-check-the-result" />

The correct connection works without changing the task’s target accidentally.

<h2 id="application-capabilities">
  6\. Application capabilities
</h2>

<span id="application-capabilities-overview" />

Before choosing an application, check its supported version, setup requirements and the operation you need. Reading a file, editing native elements and exporting a result require different capabilities.

Start with the connection guide for [Revit](/apps/contexts#connect-revit), [AutoCAD](/apps/contexts#connect-autocad), [Rhino](/apps/contexts#connect-rhino) or [Blender](/apps/contexts#connect-blender). Check the task’s inputs and output format before running it.

<span id="application-capabilities-in-ideatura" />

1. Choose the application and version.
2. Check the operation you need, including access requirements.
3. Open its setup guide.
4. Use an example verified for that combination.

<span id="application-capabilities-check-the-result" />

The chosen route supports the intended input, operation and output.

<h2 id="understand-execution-controls">
  7\. Understand execution controls
</h2>

For the relationship between execution modes and permissions, read [AI controls](/ai/controls). Verify the intended manual and autonomous action separately; a written instruction is not an enforced access restriction.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.