Apps, Presentations, Documents with Live Data
How the apps, presentations and documents your agent builds read your real data, how each person consents, and how Anchor records every connection.
What is live data?
Live data means an app, presentation or document shows what is in the source right now, not a copy from the day someone wrote it. In Anchor, each one connects directly to the systems you already use and stays current as they change: your CRM, ERP, data warehouse, ticketing system, issue tracker, support desk, billing, finance, product analytics and monitoring tools, and any other service your organization approves.
There are three sources of live data:
- MCP servers: any service that offers one, like your CRM, your data warehouse or your issue tracker.
- Anchor tables: structured data stored in Anchor. For an app, a table is the backend.
- Other Anchor files: images, PDFs, Markdown, HTML and any other file stored in Anchor.
| Source | Apps | Documents and presentations |
|---|---|---|
| MCP servers | Read and change data | Read only |
| Anchor tables | Read and write rows | Read only |
| Other Anchor files | Read any linked file | Not linked. They keep their own images. |
Every connection needs consent from the person using it, and Anchor records every one.
Why live data matters
Most of what an AI agent builds goes out of date soon after the agent finishes it. Someone pasted the numbers in, so next week they are wrong and someone rebuilds the deck. Live data removes that work.
- Always current: the number in the board deck is the number in the table. Nobody exports, pastes or rebuilds.
- One source of truth: a dashboard, a weekly report and an executive review can all read the same table. Fix a row once and all three are right.
- People act where they read: an app can write back. Approve a request, update a record or file an issue without switching tools.
- Access stays as it is: each person sees data with their own access and their own accounts. There is no shared login to manage.
- No hidden connections: every file lists what it uses, each person agrees to that list, and Anchor keeps the list for every version.
1. MCP servers
Anchor talks to other services over the Model Context Protocol (MCP), so any service that offers an MCP server can feed an app, presentation or document: Linear, Notion, GitHub, your CRM, your data warehouse, or a system you built yourselves.
- Apps read and change data: an app calls a service's tools as people use it. It can list open deals, update a record or add a comment.
- Documents and presentations only read: they call tools that only read, each time a page opens. Changing anything takes an app.
- As you, with your account: every call uses the account of the person using the file. An app never acts as its builder or as a shared account, so each person sees only what their own account can see.
- Only the tools it lists: a file can call only the tools on its list, and each person agrees to them first. See Consent.
Admins choose which MCP servers to allow
Nothing can use an MCP server until the organization's owner or a manager approves it.
- Open Manage org, then the MCP servers tab. Only owners and managers see it.
- Select Add server. Enter the server's URL, or search the list of well-known servers.
- Anchor checks how the server signs people in. Most need nothing more. Some ask for an app ID and secret, which you create in the service's developer settings.
- Select Approve.
- Anchor enforces the list: it refuses to build an app, or save a document or presentation, that names a server the organization has not approved.
- Pause with one switch: turn a server off and everything that uses it stops reaching it until you turn it back on. Anchor deletes nothing, and everyone stays connected.
- Delete to cut it off: deleting a server disconnects everyone, and Anchor asks the service to revoke their access. Everything that uses it needs a new version to work again, so pause it if you only want to stop it for now.
- Know what it affects: before you pause or delete a server, Anchor tells you how many apps, documents and presentations use it.
- Members only: only members of the organization that approved a server can use it. Someone from another organization can't, even when you share the file with them.
For sign-in details and limits, see Connecting services. If your MCP server only accepts allowlisted IPs, see IP addresses.
Each person connects their own account
Approving a server gives nobody access to it. Each person connects their own account, once per organization.
- Where to look: open the menu under your profile picture and choose Connectors. It lists every service your organizations have approved, each with a switch to connect or disconnect.
- What it shows: the date you connected, “Not connected”, or “Turned off by your org for now” when a manager has paused the server.
- When you first need it: you can also connect when you open an app or document that uses a service for the first time.
- Disconnect at any time: Anchor deletes the connection and asks the service to revoke it. Apps and documents ask for your permission again when you reconnect.
- Your sign-in stays in Anchor: Anchor stores each person's sign-in encrypted. It never reaches the app, the document or the browser.
2. Anchor tables
An Anchor table is structured, queryable data stored in Anchor. For an app, a table is the backend: the app reads and writes its rows directly, with no database to set up and no API to host. Documents and presentations read tables, so the numbers in them are the numbers in the table.
- Three ways to update a table: your AI agent fills and updates tables for you, people add and edit rows by hand in Anchor, and scripts and pipelines write to them through bot users. Everything that reads the table shows the change.
- Read and write: an app runs the queries your agent wrote for it. They can select, insert, update and delete rows. The app marks each table Read or Write, with one sentence that says what it does with the table.
- Only its own queries: the browser sends the name of a query and its inputs, never SQL. Nobody using the app can make it run anything else.
- No more access than it uses: when Anchor builds an app, it compares the app's queries with its list of tables. The build fails if a query touches a table that isn't listed, if a listed table is never used, or if the app asks for Write and only reads.
- Each person's own rows: a query can take the signed-in person's email, which Anchor fills in. An app can show each person only their own records.
- Updates as rows change: when a table changes, open documents and presentations load the new data. Apps get the same notice, so they can refresh too.
- Documents and presentations only read: their queries run when a page opens. Writing to a table takes an app.
- Same organization: an app, document or presentation can use only the tables and files in its own organization.
Someone can use a table inside an app, document or presentation without being able to open the table itself. See Access through an app, document or presentation.
3. Other Anchor files
An app can link any other file stored in Anchor: an image, a PDF, a Markdown or HTML file, a CSV or a video. The app reads the file where it is, so there is one copy and nothing to upload twice.
- Any file type: anything stored in Anchor that is not a table, app, document or presentation.
- Read only: an app can read a linked file. It can never change one.
- Only the files it lists: the app lists each linked file with one sentence that says what it does with the file. The app can't load any other file, whatever the person using it can open.
- Three ways to add a file: your AI agent creates and updates files for you, people upload them by hand in Anchor, and scripts and pipelines write them through bot users.
- Always the current file: the app loads the file as it is now. Replace a logo or a price list once, and every app that links it shows the new one.
- Each person needs view access: the app shows a file only to people who can view it. When you share an app, Anchor shares the files it links too, if you can share them.
Only apps can link other files. Documents and presentations can't. Their images are part of the document or presentation itself. For live data, they use Anchor tables and MCP servers.
Consent
Nothing connects without consent. Each person approves exactly what an app can do. The same goes for documents and presentations. Before one reads or changes anything for you, Anchor shows you everything it uses, and you agree to it.
Before you continue
Release desk will access the files below and use your accounts in the services below.
Release decisionsWrite
Adds one row for every go or no-go call.
Release checklistRead
Reads the checklist to score each release.
Linear
Finds the issues behind each release, and notes the call on them.
Connected on Oct 16, 2026
list_issuescreate_comment
- What you see: each table and file, with Read or Write and the reason. Each service, with the account it will use and every tool it calls.
- Every tool is marked read or write: the consent page labels each tool Read data only, Change data, Delete data or Reach outside the service. Anchor treats a tool with no label as one that can change data, delete data and reach outside the service.
- Everyone agrees for themselves: the person who built the app agrees too. Building an app gives nobody access to anything, and nobody can agree for someone else.
- Consent is not access: agreeing gives you nothing new. The app works with access you already have. If something is missing, you ask for it in one step, and each table's owner approves or denies it.
- Apps ask again before doing more: a new version that uses another table, file or tool, or that writes where it only read, asks again. So does a service that later says a tool can do more.
- Owners choose which connectors are allowed, and can pause any: a service can't appear on a consent page until the organization's owner or a manager has approved it. They can pause it at any time.
- Checked every time: Anchor checks access and consent on every query and every call, for as long as the file is open.
- How to stop an app: disconnect the service under Connectors, or remove the person's access to the table or the app. Either one stops it.
For how people get and lose access, see Sharing & permissions.
Automatic linkage
Anchor maps what every app, document and presentation uses, and keeps the map current. You can see every dependency, down to the table, the file and the tool. Nobody fills in a form: Anchor saves the list with each version it builds, and a file can't reach anything that is not on its list.
Where a builder sees it
- Dependencies: open the menu on any app, document or presentation and choose Dependencies. Each table and file shows its name, Read or Write, whether you have access, and what the app does with it. Each service shows the tools it uses.
- One list for each version: on an app's page, pick any version and open Dependencies to see what that version uses before you publish it.
- Open to everyone who can open the file: someone who agreed weeks ago can always check what they agreed to.
DependenciesV4
Release decisionsWriteYou have access
Adds one row for every go or no-go call.
Release checklistReadYou have access
Reads the checklist to score each release.
release-notes.mdReadYou have access
Shows the notes for each release beside its checklist.
Linear
Finds the issues behind each release, and notes the call on them.
list_issuesAgreedcreate_commentAgreed
See what uses a table or a server
- From a table: a table's sharing dialog shows who can use it through each app, document or presentation, with what that file does with the table. From there you can remove one person, the organization, or everyone.
- From an MCP server: before a manager pauses or deletes a server, Anchor shows how many apps, documents and presentations use it.
- If someone deletes a source: when a table, file or server is gone, the files that use it stop opening and say what is missing. Ask your agent for a new version that stops using it.
For the rest of how Anchor works, go back to the docs.