Skip to main content

Bossa

Stop building agents that forget.

Give your AI a filesystem. ls, grep, read, write. That's it.

📖 Documentation → bossa.mintlify.app

pip install bossa-memory · No infrastructure · Sign up, get a key, ship.

Get Started · Why Filesystem? · CLI · MCP · REST API · Examples · Docs


Your agent keeps asking the same questions.

Every session is Groundhog Day. User preferences? Forgotten. Last conversation? Gone. Project context? What project?

You've tried RAG. Embeddings. Chunking. Tuning. It's a rabbit hole—and your agent still forgets.

Claude Code and Manus figured it out: give agents a filesystem. Not vectors. Not embeddings. Files. ls, grep, read, write. Agents already know how to use them. Bossa gives your agents that filesystem—persistent, searchable, Postgres-backed—in one line.


Why filesystem over RAG?

Bossa (filesystem) Traditional RAG
grep "user preferences" Tune embeddings, pray it works
Directory structure = organization Flat vector space
Works like CLI tools agents know New abstractions to learn
Debuggable with ls, cat Black box retrieval
No embedding drift Constant re-indexing

For 80% of agent use cases, filesystems just work. Why we chose this →


Dynamic context discovery—built in.

Cursor and LangChain are moving to dynamic context discovery: let the agent pull context on demand instead of loading everything. Fewer tokens. Better answers.

Bossa is the storage layer for that. Your agent uses ls and grep to discover what's relevant, then read to pull only what it needs. No new concepts. Just files.


Get Started

30 seconds. No infrastructure. No Docker. No config.

Step Action
1 Sign up via the CLI
2 Create a workspace & API key
3 Connect your agent via MCP or REST

Base URL: https://filesystem-fawn.vercel.app
MCP endpoint: https://filesystem-fawn.vercel.app/mcp

pip install bossa-memory
bossa signup && bossa login
bossa workspaces create my-app && bossa keys create my-app
bossa workspace use my-app --key sk-...   # Store key, then:
bossa files ls /

What you get

  • Feels like local files — ls, read, write, grep, glob, edit, delete. No new concepts.
  • Powered by Postgres — Full-text search, trigrams, ACID, JSON. Enterprise-ready.
  • Plug-and-play — CLI for subprocess agents; MCP for LangChain, Claude, Cursor; REST for scripts.
  • Your agent's space — Each API key = one workspace. No cross-tenant leakage.

What can you build?

Personal AI assistant — Preferences, conversation history, project context. Never ask twice.

Customer support agent — Account info, tickets, interaction history. One source of truth.

Research agent — Sources, findings, notes. Build knowledge over weeks.

See more examples →


CLI

First-class for agents. When your harness runs tools as subprocesses, use bossa files for full parity with MCP.

bossa files ls /                    # List directory
bossa files read /docs/x.md         # Read file
bossa files grep "project alpha"   # Search
echo "content" | bossa files write /note.txt

Agent mode: BOSSA_CLI_JSON=1 for machine-readable output. Full CLI reference →


MCP Tools

Connect to https://filesystem-fawn.vercel.app/mcp. Pass Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY.

Tool What it does
ls List files and directories
read_file Read file contents
write_file Create or overwrite
edit_file Replace substring in place
grep Search with literal/regex
glob_search Find by pattern
delete_file Delete a file

MCP setup for Claude, Cursor, LangChain →


REST API

Base URL: https://filesystem-fawn.vercel.app

Method Endpoint Description
POST /api/v1/files Create or overwrite
GET /api/v1/files?path=... Read file
GET /api/v1/files/list?path=... List directory
POST /api/v1/files/search Grep search
GET /api/v1/files/glob?pattern=...&path=... Glob search
PATCH /api/v1/files Edit in place
DELETE /api/v1/files?path=... Delete

Full REST reference →


Examples

CLI (agent subprocess)

export BOSSA_API_KEY=your-api-key
export BOSSA_CLI_JSON=1
bossa files ls /
bossa files read /memory/summary.md
echo "New content" | bossa files write /memory/note.txt

LangChain + MCP

from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient({
    "bossa": {
        "url": "https://filesystem-fawn.vercel.app/mcp",
        "transport": "streamable_http",
        "headers": {"X-API-Key": "YOUR_API_KEY"}
    }
})
tools = await client.get_tools()
# Use with your agent

More examples in the repo →


Self-Hosting

Run Bossa on your own infrastructure. Self-hosting guide →


Documentation

Doc Description
Getting Started Sign up, API key, first request
Pricing & Limits Account tiers, usage limits
Why Filesystem? Filesystem vs RAG
Dynamic Context Discovery How Bossa fits Cursor & LangChain
CLI Reference Full command reference
MCP Integration Claude, Cursor, LangChain
REST API Full API reference
Agent Integration Examples, tool patterns
Self-Hosting Run on your infrastructure

License

MIT

Metadata

Release files for bossa-memory 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bossa-memory 0.1.5
File Size Uploaded Provenance Actions
bossa_memory-0.1.5.tar.gz 35.9 kB Without provenance Details for bossa_memory-0.1.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bossa-memory 0.1.5
File Interpreter ABI Platform Actions
bossa_memory-0.1.5-py3-none-any.whl Python 3 none any Details for bossa_memory-0.1.5-py3-none-any.whl

Total release size: 60.3 kB

Release files / bossa_memory-0.1.5.tar.gz

Download URL bossa_memory-0.1.5.tar.gz
Size 35.9 kB
Tags Source
SHA-256 checksum
How to use checksums
017dcddcde848ed641e40cbe6623e269f45a84eb3374f9f13219fe62ec7a6084
BLAKE2b-256 checksum
How to use checksums
7628226fbb714c63b67ade747b90cd805c5af7f6c18f39fba9b16a8de522b4f2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / bossa_memory-0.1.5-py3-none-any.whl

Download URL bossa_memory-0.1.5-py3-none-any.whl
Size 24.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f88e2203beb55ca1d1dc19fa0b879fe34f51c28ed160803836837c93ed422e73
BLAKE2b-256 checksum
How to use checksums
c5c93aea36389871c759bda9d7025762bea2aab242b463a24044a2890124bc1d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Security for bossa-memory 0.1.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page