How to build business automations by describing them: NOCA, vibe coding and MCP
By Asaf Yoshpe, CEO, CloudX
Published: Last tested:
The short answer
NOCA.AI is a business automation platform that brings forms, document generation, e-signatures, workflow automation, AI agents and integrations with systems like Salesforce, NetSuite, SAP and Priority into one place.
Three things make it relevant to working with AI:
- Building by description (vibe coding). You describe the form, app or process, and NOCA builds it.
- An MCP server. Claude, ChatGPT, Grok and any MCP-compatible assistant connect to NOCA, and can run your processes and read data straight from the chat.
- Building from the chat. With builder permissions, the assistant can also create and change processes and apps in NOCA, test them with sample data and read the run log.
In every case, NOCA runs the process itself, through the steps defined in it, with a log of every run and with the permissions you gave the assistant.
What vibe coding means in NOCA
Vibe coding is building software by describing it instead of building it by hand. NOCA uses the term for its own platform, and applies it in three places:
| What you build | What you describe | What you get |
|---|---|---|
| Forms | Fields, conditions and validations | A form with conditional logic, validation and built-in signature capture |
| Processes (Prompt to Flow) | What should happen, in what order and in which systems | A process with steps, logic, data handling and integrations |
| Apps (Prompt to App) | A portal, dashboard or internal tool | A web app with screens, logic and integrations, styled to your brand |
According to NOCA, a process is checked before it goes live: NOCA checks for missing steps, connections and inputs, runs it with sample data, and logs every run step by step.
What MCP is
MCP (Model Context Protocol) is an open standard Anthropic launched in November 2024 for connecting AI assistants to the systems where data lives: business tools, content repositories and development environments. A system that wants to be available to AI exposes an MCP server, and the assistant (Claude, for example) connects to it as a client.
According to Anthropic, the goal is secure, two-way connections between data sources and AI tools, instead of a separate integration for every source.
What the assistant can do in NOCA through MCP
NOCA's MCP server exposes 80 tools across these areas: apps, bots, flows, documents, connections and data.
Everyday use, from the chat:
- Run a published process: generate a document, request a signature, create records and trigger automations.
- Read records directly from Salesforce, Priority, SAP Business One, Dynamics 365 or SQL Server, without building a process.
- Check what happened in runs: status, timing and errors, step by step.
Building and maintenance:
- Create a process, add and change steps, validate it and run it with sample data.
- Create and change apps and forms.
- Turn a Word document into a template and map its fields, or place signature fields on a PDF.
- Build chatbots.
An example from NOCA's site: you tell Claude "Create an agreement for Acme, send it to John for signature, and update Salesforce when it's signed." NOCA generates the document, gets it signed, runs the workflow and syncs your systems.
Permissions: what the assistant is allowed to do
Permissions in NOCA's MCP server are split into four groups, each enabled separately:
| Group | What it allows | Example tools |
|---|---|---|
| Builder | Build and configure apps, flows, bots and templates | create_app, add_node, validate_flow |
| Data read | Read records, runs and bot conversations | query_records, list_runs, get_run |
| Data write | Run published flows that change data | run_flow |
| Admin | Publish, restore and delete, with confirmation for destructive actions | publish_flow, restore_app_version, delete_app |
On top of that, inside the assistant you set each tool to Always allow, Needs approval or Blocked.
The setup NOCA recommends by role:
- Sales, finance and HR users: Data read and Data write, with running a flow (run_flow) set to Needs approval at first.
- Builders and operations: add Builder, so the assistant can create and test flows and apps.
- Platform admins: Admin, with publish and delete kept on Needs approval.
Security, according to NOCA: the assistant connects through OAuth and acts as a known NOCA user, with no shared passwords. Delete and restore require explicit confirmation, and every run is logged with status, trigger, timing and errors. NOCA cites an ISO 27001 ISMS and SOC 2 Type II controls.
Example: a form comes in, a document gets signed, and a Slack message goes out
This is one of the processes NOCA describes itself: an intake form produces a service agreement, the agreement gets signed, a ticket opens and the team is notified in Slack.
What you write:
"When a client fills in the onboarding form, generate an agreement from the template, send it to them for signature, and when they sign, save the signed agreement on their Salesforce record and post a message to the onboarding channel in Slack."
What the process does:
| Step | What happens | What NOCA provides for this step |
|---|---|---|
| 1. Form | The client fills in the form | A NOCA form with conditional logic and validation |
| 2. Document | Generate the agreement from the template, with details from the form and the CRM | DOCX or PDF generation from a Word template |
| 3. Signature | Send it for signature, in signer order | NOCA e-signatures, DocuSign or GlobalSign digital signatures. Signing order and automatic reminders |
| 4. Save | Store the signed agreement and update the record status | Filing to Salesforce, NetSuite, Google Drive, Box or SharePoint |
| 5. Slack | The team gets a message | Slack integration |
If the signature should happen inside the form itself, for example a consent form, NOCA forms can capture it directly.
What we add to a process like this, from experience:
- A short Slack message. Name, status and a link to the record. No ID numbers and not the document contents. The data itself stays in the system, with its permissions.
- A path for people who don't sign. Reminders, then an alert to the owner, so a document doesn't get stuck without anyone noticing.
- Testing before publishing. Run the process with sample data before it goes live, and focus on the cases that don't go to plan.
- The signature level. NOCA lets you choose between an e-signature and a certificate-based digital signature. Which level a given document needs is a question for a lawyer.
For managers: when it fits
It fits when:
- There is a repeating process done by hand today: a form, a document, a signature, a system update and a team notification.
- The process crosses several systems, such as CRM, ERP, file storage and Slack.
- Your team already works in Claude or ChatGPT, and you want them to trigger processes and pull data without switching screens.
What still needs your decision:
- What the process should look like, including exceptions. Building is fast, but you define the process.
- Who gets which permissions in the assistant, and what requires approval.
- Who owns the process after it goes live.
For technical teams: what building through MCP looks like
Building a process from Claude, with Builder permissions, usually goes through these steps with NOCA's MCP tools:
- Discovery. Which services and connections exist (list_services, list_connections), and what each action takes and returns (get_action_schema).
- Real values. For fields that come from a list, such as a Salesforce object or a Slack channel, the assistant pulls the existing options (lookup_options).
- Draft. Create a process with a trigger (create_flow_draft), then add steps one by one (add_node).
- Validation. Check for missing triggers, connections, inputs and references (validate_flow).
- Test. Run it with sample data (test_flow), and read the run step by step (get_run).
- Publish. Make the process live (publish_flow), which requires Admin. From then on, users with Data write can run it (run_flow).
What it costs
According to NOCA's pricing page, as of our check:
| Plan | Price | Includes |
|---|---|---|
| Free | $0 | 50 credits a day (up to 300 a month), one user |
| Starter | $20 a month, as shown on the yearly view | 1,000 credits a month, 20 projects |
| Growth | $150 a month, as shown on the yearly view | 5,000 credits a month, 5 users, 50 projects |
| Scale | Custom | Credits, users, projects and environments as needed |
The binding prices are the ones published on NOCA's official site.
Want to see it working?
CloudX is a certified NOCA.AI partner. We'd be happy to show you what a form, signature and Slack process looks like, and how to run it from Claude. Book a demo, or read more about NOCA.AI at CloudX.
FAQ
What is NOCA.AI?
NOCA.AI is an AI-powered business process automation platform. It combines forms, document generation, e-signatures, workflow automation, AI agents and integrations. You build by describing what you need, and you can run processes straight from ChatGPT, Claude or Grok through its MCP server.
What is vibe coding?
Building software by describing it instead of building it by hand. In NOCA it means describing a form, process or app and getting it built and connected to your systems.
What is MCP?
MCP (Model Context Protocol) is an open standard Anthropic launched in November 2024 for connecting AI assistants to the systems where data lives. A system exposes an MCP server, and the assistant connects to it and uses the actions it is allowed to.
Can Claude build a process in NOCA?
Yes, once you give it Builder permissions. It can create processes and apps, add steps, test with sample data and read the run log. Publishing requires Admin.
Can Claude run processes and read data?
Yes. With Data write it runs published processes, and with Data read it reads records from Salesforce, Priority, SAP Business One, Dynamics 365 or SQL Server, and checks runs.
Which AI assistants work with NOCA?
Claude, ChatGPT, Grok and any MCP-compatible assistant.
Can the assistant delete data or processes?
Only if you give it Admin, and even then delete and restore require explicit confirmation. You can also set those actions to Needs approval or Blocked in the assistant.
Does the assistant see my passwords?
The assistant connects to NOCA through OAuth, with no shared passwords, and acts as a known NOCA user.
How do I know what the assistant did?
Every process run is logged with status, trigger, timing and errors, and you can open each run step by step.
Does NOCA work with DocuSign?
Yes. You can use NOCA's own e-signatures, DocuSign or certificate-based GlobalSign digital signatures, depending on the document and the level of assurance it needs.
Where are signed documents stored?
NOCA files them to Salesforce, NetSuite, Google Drive, Box or SharePoint, and updates the status on the related record.
Do I need to know how to code?
No. You build by describing what you need, and forms can also be built with drag and drop.
Sources and date checked
Details were checked on November 15, 2026 against the NOCA.AI site and Anthropic's announcement.