MCP Client vs MCP Server: How Noca Uses Both

Yes. Noca exposes tools to AI assistants as a server and uses external MCP servers in its bots and flows as a client.

In the Model Context Protocol, an MCP client is the application that uses tools, and an MCP server is the service that provides them.

Key points include: Connects to one or more MCP servers; Reads the list of available tools; Decides when to call a tool and with which inputs; Shows results to the user or uses them in its next step.

Consider the following: Publishes tools with names, descriptions and input schemas; Authenticates the client and enforces permissions; Executes the action and returns results.

Noca bots and flows can also use tools from external MCP servers, including Notion, GitHub, Stripe, Airtable, Discord, Dropbox, Firebase, Firecrawl, Pinecone, monday.com and Google Workspace services. Bots connect to them with an explicit allowlist of tools.

Yes. With the Noca MCP Server, ChatGPT, Claude, Grok and other MCP-compatible assistants can run your published Noca flows and use Noca tools for MCP client vs server, within the permission groups and per-tool approvals you set.

Yes. Noca connects natively to Salesforce, NetSuite, SAP, SAP Business One, Priority ERP, HubSpot, monday.com and 60+ other systems, so MCP client vs server can use live data from them and update them automatically.

No. In Noca you describe what you need in plain language and Noca builds the forms, apps, flows and documents. Developers can extend any process with REST APIs, OpenAPI definitions and webhooks.

Use least-privilege permissions, require approval for sensitive actions and keep a log of every run. Noca follows the TRAPS framework (Trusted, Responsible, Auditable, Private and Secure), records every flow run in integration logs and lets you control data storage for specific flows.

A first working version can often be built from a prompt and tested quickly. The total time depends on how many systems, approvals and documents are involved and how much testing your team requires before publishing.

Compare cycle time, manual steps, error rates and adoption before and after. Noca integration logs show how often each process runs, how long it takes and where it fails.

Yes. The Noca MCP Server connects ChatGPT, Claude, Grok and other MCP-compatible assistants to your Noca workspace with 80 tools for apps, bots, flows, documents, connections and data.

Tools are grouped into Builder, Data read, Data write and Admin. In your assistant, each tool can be set to always allow, needs approval or blocked, and destructive actions ask for confirmation.

Yes. The read-only query_records tool reads records from Salesforce, Priority, SAP Business One, Microsoft Dynamics 365 and Microsoft SQL Server without building a flow.

Yes, by running published Noca flows with the run_flow tool, which requires the Data write group. The flow keeps your validation and mapping, and you can require approval for each run.

Yes. Noca bots and flows can use external MCP servers such as Notion, GitHub, Stripe, Airtable and Google Workspace services, with an explicit allowlist of tools.

Noca is an AI-powered business process automation platform that combines forms, document generation, e-signatures, workflow automation, AI agents and 60+ integrations, with an MCP server for ChatGPT, Claude and Grok.

No. Noca builds apps, flows, bots and documents from plain-language prompts; developers can extend them with APIs and webhooks.

Noca follows the TRAPS framework (Trusted, Responsible, Auditable, Private and Secure), with permissions, approvals and integration logs.