Docs

What is Anchor?

Anchor is a system of record that AI agents and humans use together to create, host, and manage tables, apps, and all kinds of files. Connect your agent — Claude, ChatGPT, Gemini, Codex, or any other — using MCP, describe what you need, and it builds it in Anchor. You review, share, and collaborate with humans and AIs.

Think of it as Google Drive, but the items are a new generation: fully functional apps, live interactive tools, structured tables, and any file type you need. Everything lives at anchor.cc and works in any browser on desktop or mobile.

File types

Everything in Anchor is a file. Two types are unique to Anchor — tables and apps — and beyond those, you can store any ordinary file type you already work with. Each one gets a stable URL you can link to, bookmark, or share.

Tables

Tables are structured, Excel-like data at anchor.cc/table/<tableID>. Your AI agent is fully connected to them, which means you can:

• Create and edit schemas — add or rename columns, change types, reorganize.
• Query, filter, and sort rows in natural language. No formulas, no SQL.
• Transform and analyze — group, aggregate, pivot, join, or derive new columns from existing ones.
• Visualize — ask for charts, summaries, and breakdowns.

Tables also serve as the data layer for Anchor apps (covered next). A single table can power multiple apps at once — your CRM, your pipeline dashboard, and your weekly report can all share the same source of truth.

Apps

Apps are fully custom, mobile-friendly web applications. Each app has two URLs:

• The app lives at <slug>.anchor.cc — a subdomain per app. That's the link you send to whoever should open and use the app.
• The management page at anchor.cc/app/<appID> is where you see the app's version history, manage sharing, and review its connections to tables and files.

An app can connect to zero or more Anchor tables. Connect it to tables and you get a full-stack tool — CRMs, task trackers, dashboards, finance trackers, event planners — where the app and its tables stay in sync automatically. Without tables, apps work great for visual and informational content like styled documentation, charts, flow diagrams, and interactive presentations.

Apps are versioned. Your agent proposes changes, you review, and you commit — the previous version stays in history so you can roll back.

Regular files

Beyond tables and apps, you can store any ordinary file — PDFs, images, CSVs, code, markdown, and more. Each one gets its own page at anchor.cc/file/<fileID> where it can be viewed in the browser or downloaded. Your agent uploads files for you, and you share them just like anything else in Anchor.

Supported file types

Anchor recognizes these file types and renders them natively in the browser. Unrecognized types can still be uploaded and downloaded.

Uploading

Files can be uploaded by your AI agent or directly through the Anchor UI. The upload destination is always a folder — jump to any folder's upload dialog with anchor.cc/folder/<folderID>/upload.

Structure: orgs, folders, files

Anchor organizes everything into three layers.

Organizations

An organization is the top-level boundary — your team, company, or any group that works together. Every org has three roles:

• Owner — full control. Can manage members, rename, delete, and transfer ownership of the org.
• Manager — can add and remove members, invite new people, and rename the org.
• Member — can see the org roster. Cannot manage members or change org settings.

Org roles are purely administrative — they control who can manage the org itself, not who can see its content. Content access must be granted separately at the folder or file level.

Folders

All content lives inside folders. Folders always belong to an organization and can be nested to any depth. Every folder has its own permissions: an owner, contributors (can view and edit), and consumers (view only).

Files

Tables, apps, and other file types all live inside folders. Files inherit access from their parent folders, but you can also grant additional access directly on any file — for example, sharing a single file with someone who doesn't have access to the folder it lives in. See Sharing & permissions for the full details.

Sharing & permissions

Nobody gets access to anything automatically — someone always has to explicitly share it with them. Being in an org doesn't mean you can see its content.

Three roles, everywhere

Every folder and every file uses the same three roles:

• Owner — full control. Can edit, share, transfer ownership, and delete.
• Contributor — can view, edit, create sub-items, move, copy, and invite others.
• Consumer — can view and copy. Cannot edit, move, delete, or see who else has access.

Additive inheritance

Folder permissions flow down to subfolders and files. If someone is a contributor on a parent folder, they're a contributor on everything inside. The highest access level always wins.

Who can see the permissions?

Consumers see only the owner of a file and their own role. Contributors and owners see the full list of who has access.

Shared with me

When someone shares a file or folder with you — whether it's from another org or a subfolder you don't otherwise have access to — it appears in your Shared with me view.

Invite by email

You can invite anyone as a contributor or consumer by email, even if they don't have an Anchor account yet. They'll gain access when they sign up.

Connections

Apps depend on tables and files to function. These dependencies are called connections. When your agent creates or edits an app, it declares which tables and files the app needs, and at what access level.

Access levels

Connections come in two flavors — the same two roles used for human access:

• Consumer — read-only. The app can query and display the data but cannot change it.
• Contributor — read and write. The app can create, update, and delete rows or content in the target file.

Lifecycle & approval

Connections may activate instantly or require approval, depending on your role on the table or file:

• If you're a contributor or owner of the table or file, the connection is granted instantly.
• If you're only a consumer, you'll need to request the connection. An owner or contributor on that table or file must approve it before the app can use it.

Managing connections

Every app's management page shows which tables and files it depends on. Every table and file shows which apps are using it. From either side, owners and contributors can approve, deny, or revoke access.

Plans & billing

Billing in Anchor is tied to the organization, not the individual. There's no per-seat pricing: an org pays one price that covers everyone in it.

Plans are per org

Every organization is on a plan — Free, Pro, Business, or Enterprise. Upgrading or downgrading applies to that org only. See pricing for the current tiers and limits.

Limits are per org

Each org has its own usage limits based on its plan. These include:

• The number of team members in the org.
• The number of rows across all tables.
• The number of apps and tables the org can host.
• Storage — total file size across the org.
• Monthly platform usage — reads, writes, and agent actions.

Shared content

Items that another org has shared with you don't count toward your org's limits; they stay billed to the org that owns them.

Connecting your AI agent

Anchor is built for collaboration between humans and AI. Your AI agent builds tables, creates apps, and uploads files. You review, share, and use everything on anchor.cc.

This works by connecting your favorite agent to Anchor via the Model Context Protocol (MCP) — the open standard for AI tool use. Any MCP-compatible agent works: Claude, ChatGPT, Gemini CLI, Codex, and more.

For setup instructions and the full list of supported agents, see Supported Agents.

Account deletion

If you'd like to delete your Anchor account and all associated data, email support@anchor.cc from the email address linked to your account.