MCP FAQ

Common questions about the Noloco MCP server.

Can I connect multiple AI clients with the same Noloco account? Yes. Each client (Claude Desktop, Claude Code, Cursor, Windsurf, etc.) runs its own OAuth sign-in and gets its own token. They can all be connected at once, and each can have a different scope or set of approved apps.

Does using the MCP server count against my API rate limits? Yes. MCP tool calls go through the same Noloco data API as Zapier, Make, and direct REST calls. They are subject to the same rate limits as your plan.

Can the AI see data from all my Noloco apps? Only the ones you approve. During sign-in you pick which apps the client can access; by default it's every app where you're a data admin. You can re-run the consent flow at any time to add or remove apps.

What happens if the AI tries to do something it shouldn't? The MCP server enforces the same data validation as the rest of the Noloco API. Required fields, field type constraints, and relationship rules all apply. Every tool call is also checked against your live data admin role on the target app — losing access takes effect immediately.

Can I revoke access for a specific AI client without affecting others? Yes. Each client has its own OAuth token. Revoke it from your Noloco connected applications and that client stops working immediately while your other clients keep running.

Does the MCP server give the AI access to my app's pages and UI? No. The MCP server exposes data only — tables, fields, and records. It does not give the AI access to your app's pages, views, workflows, or settings.

Is there an extra cost for using the MCP server? No. MCP access is included in all Noloco plans that have API access. Check your plan limits if you are unsure whether your plan includes API access.