Working with your AI assistant in Laplace

An AI assistant is more useful when it can work with the project you are actually building. It needs the source, the right tools, and a clear sense of what you want to change. You need a way to see the result and decide whether it is ready for other people.

Laplace brings those steps into a shared workspace. You can use your preferred compatible assistant, keep the project in one place, and review its work alongside your collaborators. Connecting an assistant does not publish an app or hand it every account in your organization.

Start with one useful project

Choose a focused job: track campaign deliverables, collect requests, or give a team a simple dashboard. Start with a Laplace template, or bring supported source from a GitHub repository. An imported project may need adaptation to the supported runtime; importing source is not a guarantee that every existing application can run unchanged.

Open the app workspace and get familiar with Preview, suggestions, and collaborators. Preview is where you try changes. Live is the version you have chosen to publish. Your connected assistant works with the authorized project tools; the workspace gives people a place to review the result and propose improvements.

You can describe the intended outcome before asking an assistant to edit anything. A short project description and a concrete first task are often enough to make the next step clear.

Connect the assistant you already use

Laplace uses MCP, the Model Context Protocol, to make authorized tools available to compatible AI clients. The How To area provides the configured MCP server address and installation instructions. Use the instructions for your client, then complete its connection and authorization flow.

Give the client your app's workspace link and explain the work you want it to do. The Share menu lets you copy that link. Keep the project request separate from credentials; you do not need to paste API keys, vault values, or access tokens into a prompt.

Authorization matters at each step. Your client needs the relevant project access, and organization tools follow their own access rules. A connection setting is not proof that an assistant has successfully completed a task. Check the result in the workspace.

Ask for a change you can review

Give the assistant a bounded task. For a campaign tracker, that might be: “Add a status filter, keep the existing records, and show an empty state when no campaigns match.” Explain what should happen, what needs to stay intact, and how you will check it.

As the assistant updates source, review its changes through your assistant or repository and try the latest Preview. Successful source updates refresh Preview automatically. If a build fails, the workspace can retain the last successful preview and indicate that it is outdated. Look at the current status before treating what you see as the latest result.

Use suggestions to collect improvements from collaborators and follow the reported agent activity. An editor can review and approve a suggestion for their assistant to implement. These records complement your own review; they do not replace trying the important interactions or checking whether the app solves the intended problem.

Keep connected accounts deliberate

Connections and profiles organize the accounts your organization uses. Owners and admins manage these accounts, custom connections, and project secrets. Profiles can group existing connections for a project or environment without making another copy of each account.

Organization MCP tooling and app runtime integrations have different permission boundaries. A provider appearing in the catalog does not mean every action is available inside an app. Current app connection grants support approved QuickBooks company-information and read-query actions. Decide what information the app should expose before sharing it.

Store credentials in the encrypted secret vault rather than in source or shared messages. When someone needs a secret, use an expiring share link and revoke future access when the work is complete. Revoking a link cannot take back a value someone has already received.

Publish when the work is ready

Try the app's main workflow, inspect the changes, and check the current build and runtime status. These checks help establish that the revision builds and runs; they do not automatically prove that every interaction, layout, or business rule is correct.

Publish captures a source revision and checks a separate candidate before promoting it. You can continue working while publication runs. Preview and Live remain separate, so an unfinished change does not become the version collaborators use simply because it was saved.

Invite people with Can view or Can edit access according to their role. Apps start private, and invitations can include collaborators outside your organization. Use the shared workspace to keep people, assistants, and access decisions close to the project as it develops.

Explore the Laplace workspace, compare Pro and Enterprise, or talk to us about your setup.