
Claude Code
Start in your project folder and use MainPath skills to create projects, import code and develop locally.
Keep building with Claude Code, Codex or Cursor. MainPath connects your agent to project structure, tests and releases, so the next prompt becomes a project change you can follow.
The agent plugin brings skills, rules and MCP tools into the environment you already use.

Start in your project folder and use MainPath skills to create projects, import code and develop locally.

Give your agent a prepared project foundation and let it work on changes with the matching workflow.
Work on your project in the editor and use MainPath tools directly with your agent.
Install the MainPath CLI and agent plugin. Sign in, then reload your editor or agent.
Create a project from a template. For existing code, your agent first checks whether the stack is supported for import.
Describe the next change. Review the code, try it locally and let tests and builds check the new version before you approve it.
A prepared structure and conventions give your agent a starting point. Add your own rules in the project.
Automated tests and builds check new commits. See when a change fails and work through it with your agent.
Environment configuration lives in the Git history. Follow changes and decide which version to approve.
Open your project locally or use a prepared workspace. Project structure, rules and versioned code remain the shared foundation for you and your agent.
Connect your agent, start a project and build on a prepared structure. You continue to obtain your agent licence from its provider.
The MainPath CLI installs the agent plugin with skills, rules and MCP. Sign in, then reload your editor or agent. Open the parent project folder so your agent can see the repositories that belong to it.
Yes, when the stack is supported. Your agent checks the local folder and guides the import into MainPath. For an unsupported framework, it reports the limitation rather than rebuilding your project in a different stack.
Tests and builds show whether the configured checks pass. You or your team still review whether the change meets the intended requirements and covers the important cases.
You choose the project credentials and appropriate access. Review your agent’s changes and decide when to approve a version. Project rules support this workflow; they do not replace a review of the changes.
The MCP server runs through the MainPath CLI in the local working environment. A cloud agent without access to that installation cannot use this local connection. Project creation and imports need an agent with the corresponding connection.