Noloco for AI agents
Noloco is a no-code platform for building internal tools, client portals, and business applications backed by a dynamic GraphQL data API. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Noloco.
Look up a record
Read a specific record from a table to answer a question, without changing anything.
Create a new record
Create a record in a table after a new item is submitted through a portal.
Approve before deleting a record
Require approval before deleting a record, since it may be referenced by other linked data.
7 Noloco actions, graded by risk.
Every Noloco action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- noloco.get_recordGet Record
- noloco.list_tablesList Tables
- noloco.list_recordsList Records
- noloco.describe_tableDescribe Table
write
2Create and change things. Allow, or ask the user first.
- noloco.create_recordCreate Record
- noloco.update_recordUpdate Record
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- noloco.delete_recordDelete Record
Noloco in three steps.
- 01Your users connect NolocoThey add their Noloco api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Record” can wait for the user, and “delete Record” can be denied outright.
- 03Any agent can actYour agent calls Noloco through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('noloco', { read: 'allow', write: 'ask', // create_record destructive: 'deny', // delete_record }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Noloco connects.
Users add their Noloco api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Noloco connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Noloco from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Noloco and Arc0, answered.
Can I use Noloco with Claude, ChatGPT or Cursor?
Yes. Connect Noloco to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Noloco actions you allow.
How do users connect Noloco?
Users add their Noloco api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Noloco actions can my agent take?
7 in total: 4 read, 2 write and 1 destructive, such as “create Record”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Noloco?
Yes. Actions like “delete Record” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Noloco too?
Yes. The same Noloco connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Noloco into your agent.
Your users connect Noloco once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan