Bika.ai for AI agents
Bika.ai is an AI-powered database and automation platform, used by teams to store structured records, run automations, and trigger webhooks across spaces without writing code. 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 Bika.ai.
Check a database's schema
Get a database's schema to confirm field names before writing new records into it.
Add new records to a table
Create records in a table from incoming data, such as new leads or tasks.
Delete records carefully
Delete records flagged as duplicates only after a person confirms which ones are safe to remove.
8 Bika.ai actions, graded by risk.
Every Bika.ai action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- bika_ai.get_recordGet Record
- bika_ai.list_nodesList Nodes
- bika_ai.list_spacesList Spaces
- bika_ai.list_recordsList Records
- bika_ai.get_database_schemaGet Database Schema
write
2Create and change things. Allow, or ask the user first.
- bika_ai.create_recordsCreate Records
- bika_ai.update_recordsUpdate Records
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- bika_ai.delete_recordsDelete Records
Bika.ai in three steps.
- 01Your users connect Bika.aiThey add their Bika.ai api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Records” can wait for the user, and “delete Records” can be denied outright.
- 03Any agent can actYour agent calls Bika.ai through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bika_ai', { read: 'allow', write: 'ask', // create_records destructive: 'deny', // delete_records }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Bika.ai connects.
Users add their Bika.ai 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 Bika.ai 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 Bika.ai from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore databases and spreadsheets apps.
Bika.ai and Arc0, answered.
Can I use Bika.ai with Claude, ChatGPT or Cursor?
Yes. Connect Bika.ai 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 Bika.ai actions you allow.
How do users connect Bika.ai?
Users add their Bika.ai 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 Bika.ai actions can my agent take?
8 in total: 5 read, 2 write and 1 destructive, such as “create Records”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Bika.ai?
Yes. Actions like “delete Records” 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 Bika.ai too?
Yes. The same Bika.ai connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Bika.ai into your agent.
Your users connect Bika.ai once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan