Made with Hope

Tools reference

The Bit Cloud MCP server exposes tools that let AI agents discover, inspect, and browse your components, scopes, apps, and lanes. All tools require authentication.

Typical workflow: search with search_components, review with read_components, then read source with read-file when needed.

Discovery

orientation

Get a high-level overview of all scopes in a Bit account. Use this as a starting point to understand the organization's domain structure.

ParameterTypeRequiredDescription
ownerstringyesBit account name (e.g., acme, teambit)

search_components

Search for components across an account's scopes. Use specific terms — avoid generic words like "component" or "ui".

ParameterTypeRequiredDescription
queriesstring[]yesArray of search queries (e.g., ["date picker", "form validation"])
ownerstringnoBit account to search in. Defaults to the token's account.

Scopes

read_scope

Read scope metadata, aspect configuration, and its first 25 components. For scopes with more components, use list_components to paginate.

ParameterTypeRequiredDescription
scopeIdstringyesScope ID (e.g., acme.design, bitdev.base-ui)

list_components

List components in a scope with pagination. Returns slim component info — ID, description, and package name.

ParameterTypeRequiredDescription
scopeIdstringyesScope ID to list from
offsetnumbernoNumber of components to skip (default: 0)
limitnumbernoMax results to return (default: 25, max: 50)

Components

read_components

Retrieve full component details — dependencies, API reference, documentation, and file paths. Use search_components or list_components to find component IDs first.

ParameterTypeRequiredDescription
componentIdsstring[]yesComponent IDs to inspect (max 10). e.g., ["acme.design/actions/button"]
includeApiReferencebooleannoInclude exported types and function signatures (default: true)
laneIdstringnoLane ID for lane-specific versions

read-file

Read the source code of a specific file in a component. Use read_components first to discover available file paths.

ParameterTypeRequiredDescription
componentIdstringyesComponent ID, optionally with version (e.g., acme.design/actions/[email protected])
filePathstringyesFile path within the component

Apps

list_apps

List deployed applications for an account.

ParameterTypeRequiredDescription
ownerstringnoBit account to list apps from. Defaults to the token's account.
laneIdstringnoLane ID for lane-specific app versions

Lanes

list_lanes

List lanes with filtering options. Returns lane metadata including component count, status, and creation date.

ParameterTypeRequiredDescription
ownerstringnoFilter by account owner
scopesstring[]noFilter by scope IDs
usersstring[]noFilter by lane author usernames
searchstringnoSearch by lane name or ID
deletedbooleannoInclude deleted lanes (default: false)
limitnumbernoPage size (default: 20)
offsetnumbernoPagination offset

read_lanes

Read full lane details — metadata and the components on the lane.

ParameterTypeRequiredDescription
laneIdsstring[]yesLane IDs to read (e.g., ["acme.accounts/fix-login"])

edit_lane

Update a lane's description or display name. Requires a user token — organization access tokens cannot modify lanes.

ParameterTypeRequiredDescription
laneIdstringyesLane ID to edit (e.g., acme.accounts/fix-login)
descriptionstringnoUpdated description
displayNamestringnoUpdated display name

Next steps