Grok / xAI
Use a configured xAI provider in Astir, with Becki connected for project memory. This is a provider route, not a verified Grok.com MCP connector.
03 / Connect your AI
One account.
A working connection.
Install Becki and connect each client you use. Then check that the agent can retrieve your context and save new work. Installing the server alone does not do that.
Use Core or Astir to work with Becki. For an existing client, jump to its connection steps. Already connected? Add the memory protocol and verify with real context.
01 / Two routes
A model in Astir.
Or memory in your client.
OpenAI
Use an OpenAI model in Astir, or connect Becki to Codex or ChatGPT using the client instructions below.
Claude
Use a configured Claude provider in Astir, or connect Claude Code, Desktop or claude.ai directly to Becki.
Provider credentials and model access depend on your setup. Astir's Connections manages providers, tools and MCP servers inside the workspace. External AI clients need their own Becki connection.
02 / Install
Give Becki
a place to run.
Core / Windows, macOS, Linux
The published $15/mo memory daemon uses two npm packages: becki-mcp is the MCP server; becki is the terminal admin interface. No meeting capture or native Mac workspace.
- Sign in to Account → Install → Generate install token. Keep the token private.
- Install the packages, then run initialization and paste the token only when prompted.
- Add the MCP snippet printed by initialization to your client's configuration. It is generated for your installation; do not guess a path or paste someone else's token.
- Use the
beckiadmin interface for watched folders, backfills, token rotation and subscription management.
npm install -g becki-mcp becki
becki-mcp init # registers projects, prints MCP config snippet
becki # admin TUI: paste install token, run backfillsOptional history backfill: the source guide's command walks 90 days of Claude Code, Codex and Cursor session logs. Review which work you are authorizing before running it.
becki-mcp bootstrap 90Astir / Mac with Apple silicon
Astir brings your agent workspace and Becki's memory together. Use the installer requirements for the release you download.
- Sign up for Astir using the existing subscription route.
- Get the current Astir Mac installer from the download portal and follow its installation steps.
- Connect the Becki account you use for your memory.
- Review Connections for the providers, tools and MCP servers you want to enable.
- Review microphone, calendar and screen/audio-capture permissions when using those features. You can decline a permission; installing the app does not grant it.
Keep your existing Becki account and vault. Configuring Astir is separate from registering Becki in another editor or chat client.
Review the Astir plan03 / Connect per client
Pick the client
you actually open.
Claude Desktop, Claude Code, Cursor, Zed and Raycast
Core users use the snippet printed by becki-mcp init. A connection configured inside Astir does not automatically register these external clients.
- Open the client's MCP configuration and use the entry generated for your Core installation, or its supported authenticated remote connector.
- Restart the client if it loads configuration at startup.
- Authenticate with your Becki account when requested.
- Confirm that the client lists the Becki server and tools, then ask the verification question below.
Becki's remote endpoint is below. Use it only with a client that supports this transport and authentication. Do not guess an application-bundle path.
https://mcp.becki.io/mcpCore users: use your initialization output for local stdio setup. Claude Code can also use the skills pack in the protocol section.
Codex CLI, IDE extension and desktop
- Use the configuration snippet from
becki-mcp initfor local Core setup, or Codex's supported remote MCP configuration with your Becki account. - Restart the Codex client or IDE after changing its MCP configuration.
- Confirm Becki's tools appear, then ask what it knows about your current project.
- Add the protocol or install Becki's skills so future sessions retrieve and capture meaningful context.
The source guide covers Codex CLI, the VS Code / JetBrains extension and Codex desktop. The cloud sandbox at chatgpt.com/codex cannot reach a local MCP server. Do not treat local registration as a cloud-sandbox connection.
ChatGPT's browser connector is a separate route, with its own developer-mode setup in the next tab.
ChatGPT in the browser
- Turn on developer mode in your ChatGPT account.
- Add a new connector and use Becki's remote MCP endpoint below.
- Sign in with your Becki account when the consent screen appears.
- Enable the connector for the conversation and ask the verification question.
https://mcp.becki.io/mcpAvailability depends on the ChatGPT account's connector and developer-mode support. These steps are for web ChatGPT, not a promise of ChatGPT Desktop or Codex cloud access.
Claude.ai in the browser
- Open Settings → Connectors → Add custom connector.
- Paste the endpoint below.
- Sign in with the same Becki account you use for Core or Astir and review consent.
- Use the connector in a conversation and verify that it returns your actual context.
https://mcp.becki.io/mcpThe published FAQ also describes access from the claude.ai phone app. Use your authenticated account and confirm the connector is available in the session; this is not a mobile recording app.
Perplexity
- Check your plan. The published guide requires Pro, Max or Enterprise for custom connectors, not the free tier.
- Open Settings → Connectors → Add custom connector.
- Use the remote MCP endpoint below and sign in with your Becki account.
- Enable the connector and verify a question against your own project history.
https://mcp.becki.io/mcpA paid client plan is separate from your Becki subscription. It does not grant access to another person's vault.
Antigravity CLI / agy
The newer published guide uses Antigravity in place of the older Gemini CLI references. It has its own configuration keys and files.
- Register the server in
~/.gemini/config/mcp_config.json. The key isserverUrl, noturlorhttpUrl. Merge this entry into your existing file rather than overwriting unrelated servers.
{
"mcpServers": {
"becki": {
"serverUrl": "https://mcp.becki.io/mcp"
}
}
}2. If you want Becki tools available in background sessions, review this permission rule for ~/.gemini/antigravity-cli/settings.json. It allows all tools on the Becki server without per-call prompts; enable it only if that scope matches your authorization.
{
"permissions": {
"allow": ["mcp(becki/*)"]
}
}3. Authorize Becki in each interface you use. The desktop and CLI read the same MCP registration but retain separate sign-in tokens. Review each configuration; connecting Astir does not grant access in Antigravity.
Becki's VS Code sidebar extension
VS Code can be an MCP client. Becki also has a separate Marketplace extension for memory in the sidebar.
- Open Extensions and search for Becki, or use the command below.
- Use the extension's Connect action on first launch. It talks to Becki's remote server.
- Check Briefing, This Project, Commitments and Ask. If they show unexpected zeros, first confirm you are signed in.
code --install-extension becki.becki-vscodeInstalling the sidebar extension is not the same as configuring MCP for another agent inside the editor. Use that agent's own connection setup when required.
04 / Use the memory
Connected is not
the same as remembering.
Install the workflows
Astir can use skills in its agent workspace. For external clients with Core, install the Becki plain-text skills pack with the command below. No sign-in is needed to install the pack.
becki skills installThe pack covers catching up, capturing decisions, reconciling the ledger, recording rejected options, handoffs, tracing evidence, voice and source-aware code work. Skills call Becki's MCP tools; they do not create a second memory store.
Keep your edited skills. With Core, use --force only if you intend to replace your edits with the shipped version.
Or add an explicit protocol
The block beside this is copied from the published shorter protocol. Read its standing authorization before adding it to your agent rules, such as Cursor Rules or Zed AI settings. It authorizes storing work context, not secrets.
For Claude Code, the guide uses project CLAUDE.md or global ~/.claude/CLAUDE.md. Review the standing authorization before adding it. Installing a skill does not itself grant permission to ingest private work.
Use the `becki` MCP tools as your shared memory.
Standing authorization from me, the user: I authorize my AI tools to
store my project and work context in my Becki vault. My vault is my own
account. This authorization never extends to secrets, credentials, or
keys, which must not be stored anywhere.
- Query `becki_context` before any non-trivial task.
- Call `becki_ingest` after work worth remembering (decisions, dead
ends, commitments, open loops, include the WHY).
- When the user references prior context, query Becki before asking
them to re-explain.
- Remember/forget instructions take effect immediately.Resolve a tracked task when it is done. If a decision changes, save the new reasoning and link it to the decision it replaces. That keeps completed work and old choices from appearing as current.
05 / Verify & troubleshoot
Ask for evidence.
Not a connection badge.
Open a connected client and ask the question below from the setup guide. Check that the answer uses real context from your work. If your vault is empty, you may need to authorize a project backfill first.
What does Becki know about me?The agent says there is no Becki tool.
In Astir, review the enabled Becki MCP connection in Connections. In an external client, review that client's MCP configuration and authentication, then restart it if required. In Core, check the snippet from initialization. A working server in one client does not mean every client has been configured.
The client is connected, but the vault looks empty.
First check that you are signed into the intended Becki account. In the VS Code extension, use Connect. Then check whether the project has been ingested and whether the agent has been capturing meaningful context.
Review the projects and history you want to ingest before authorizing a backfill. A connection badge alone does not establish that project history exists in the vault.
Queries return weak or incomplete context.
Confirm the relevant project is enabled and present in the vault. Ask about a specific decision rather than a broad summary. Compare the result with in-app Ask Becki, which uses hybrid retrieval; some MCP clients trim results. Install skills or rules so the agent retrieves before work and captures afterwards.
Meeting transcripts are blank or CPU stays busy.
Astir needs the relevant microphone and audio-capture permissions. Without audio capture, the remote side of a call may be missing. Review capture and transcription status in Meetings. Meeting capture is not a Core feature.
Memory contains an old decision and its replacement.
Becki's memory review proposes possible supersessions; it does not silently apply them. Ask a connected agent to review proposals. Approving ranks the older entry below the newer one without deleting history. Rejecting leaves both in place. Unreviewed proposals wait.
06 / Know the data path
Local capture.
Connected retrieval.
Local transcription processes audio on your device; configured cloud transcription sends audio to the selected provider. Synced vault text supports remote MCP retrieval, and selected context can be processed by configured AI providers. Becki is not zero-knowledge. Review the chosen feature, provider terms and account settings before sharing sensitive work.
Read Trust, Security and Privacy before authorizing ingestion or broad tool permissions. Do not place API keys, passwords or install tokens in memory prompts.
For export, account controls or current client support, contact support@becki.io.