Integration

Bika.ai integration

Bika.ai is an AI organizer whose spaces hold databases, automations, forms, dashboards and documents. With this API an agent can list spaces and their nodes (resources), read a database's fields and views, list, read, create, update and delete records, upload attachments for attachment fields, and manage a space's roles, teams and members. Plans differ in OpenAPI rate limit (Free 2, Plus 5, Team and Business 10 requests per second) and monthly API requests (Free 100, Plus 100,000, Team 500,000, Business 2,500,000). Not exposed: embed links (public share URLs), automation trigger listing and run cancelling, creating outgoing webhooks, and the deprecated v1 record routes (replaced by the record tools here). Member emails and avatars, webhook callback URLs, attachment storage paths and the caller IP echoed by the system meta route are not returned; attachment values inside record fields do come back with their file URL. Authentication is a personal API token from your Bika.ai user settings, sent as a Bearer token.

Connect Bika.ai How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Bika.ai.Built from the 31 Bika.ai tools below, on the connection you add once.

What you can do with Bika.ai

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Record, 7 operations

create_recordsCreate recordsPOSTCreates up to 10 records in a database for real; database automations watching new records may run. Returns the created records with their IDs.
delete_recordDelete recordDELETEDeletes one record of a database for real. Returns the record ID with deleted true or false.
delete_recordsDelete recordsDELETEDeletes up to 10 records of a database for real. Returns each record ID with deleted true or false.
get_recordGet recordGETGets one record of a database by record ID, with all its field values.
list_recordsList recordsGETLists records of a database, up to pageSize per call. When hasMore is true, call again with offset set to the returned offset. Supports a filter expression, field selection and one sort.
update_recordUpdate recordPUTUpdates one record of a database for real; automations watching record changes may run. The vendor does not say whether fields left out are kept or cleared. Returns the updated record.
update_recordsUpdate recordsPUTUpdates up to 10 records of a database for real; automations watching record changes may run. The vendor does not say whether fields left out are kept or cleared. Returns the updated records.

Role, 4 operations

create_roleCreate rolePOSTCreates a role in a space for real. Members given this role get its space permissions. Returns the new role and its ID.
delete_roleDelete roleDELETEDeletes a role from a space for real; its members lose the permissions it granted.
list_rolesList rolesGETLists the roles of a space with their space permissions and member counts, one page at a time (pageNo, pageSize; total gives the count).
update_roleUpdate rolePUTUpdates a role for real, changing what its members can do in the space. Leave a param out to keep it; send permissions as the complete list wanted.

Team, 4 operations

create_teamCreate teamPOSTCreates a team (department) in a space for real, at the root or under a parent team. Returns the new team and its ID.
delete_teamDelete teamDELETEDeletes a team (department) from a space for real.
list_teamsList teamsGETLists teams (departments) of a space, one level at a time: the root teams, or the sub-teams of parentTeamId. Paged with pageNo and pageSize; total gives the count.
update_teamUpdate teamPUTRenames a team of a space for real. Returns the updated team.

Member, 3 operations

delete_memberDelete memberDELETERemoves a member from a space for real; the person loses access to the space.
get_memberGet memberGETGets one member of a space: name, nickname, user ID, guest and owner flags. Email and avatar are not returned.
update_memberUpdate memberPUTUpdates a space member for real: name, teams and roles. Changing roles or teams changes what the member can access. Leave a param out to keep it.

Node, 2 operations

get_nodeGet nodeGETGets one node (resource) of a space by ID: its name, type and parent folder.
list_nodesList nodesGETLists the nodes (resources) of a space: databases, automations, forms, folders, documents and more, with ID, name and type. A DATABASE node's id is the databaseId for the record tools.

Outgoing webhook, 2 operations

delete_outgoing_webhookDelete outgoing webhookDELETEDeletes an outgoing webhook of a space for real; its callback stops receiving events.
list_outgoing_webhooksList outgoing webhooksGETLists the outgoing webhooks registered in a space with ID, name, description and event type. Callback URLs are not returned.

Space, 2 operations

get_spaceGet spaceGETGets one space: name, slug, owner, creation date and main settings (join rule, default resource permission).
list_spacesList spacesGETLists the Bika.ai spaces the token's user belongs to, with each space ID (needed as spaceId by every other tool), name, owner and main settings.

Attachment, 1 operation

upload_attachmentUpload attachmentPOSTUploads a file to a space and returns its attachment id and name. Put that {id, name} object in an attachment field with create_records or update_record; the upload alone attaches nothing.

Database, 1 operation

get_databaseGet databaseGETGets a database: its ID, name and space ID. Use list_database_fields for its columns and list_database_views for its views.

Database field, 1 operation

list_database_fieldsList database fieldsGETLists the fields (columns) of a database with ID, name, type and select options. Read it before writing records: record fields are keyed by field name (or ID with fieldKey=id).

Database view, 1 operation

list_database_viewsList database viewsGETLists the views of a database (grid, gallery, kanban, gantt or form views) with ID, name and type.

System meta, 1 operation

get_system_metaGet system metaGETReturns the Bika.ai platform version and build (no token needed). Use it as a connection check.

Team member, 1 operation

list_team_membersList team membersGETLists the members of a team, one page at a time (pageNo, pageSize; total gives the count). Emails and avatars are not returned.

User profile, 1 operation

get_user_profileGet user profileGETReturns the profile of the user who owns the API token: ID, name, email, time zone, locale and account status.

Use Bika.ai from Claude Code, Cursor or Codex

Connect Bika.ai in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Bika.ai operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Bika.ai

Create your workspace
Sign up free. Nothing to install.
Connect Bika.ai once
Add your Bika.ai connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.