Grist

MCPAI代理

提供方 gristlabs

AI代理 HTTP · 远程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorGemini CLI
查看接入方式

Grist is a flexible spreadsheet-database. The Grist MCP server lets agents work across your team sites and documents: list and query records, add or update rows, create new docs and tables. Universal URL with OAuth 2.0. Works in Claude, ChatGPT, and any MCP client that supports r

一句话选型结论

按资料字段整理

Grist 属于AI代理类 MCP 服务器,HTTP · 远程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

spreadsheet database no code productivity oauth remote

支持客户端

适用场景

spreadsheetdatabaseno code

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
https://docs.getgrist.com/api/mcp

把它填进客户端的 MCP 配置即可,不需要在本地安装运行时。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Grist当前 未标注 HTTP · 远程 远程部署 有 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方gristlabs上游标注的维护方 gristlabs
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

47.9 KB
来自项目仓库与上游目录的原文,未做删改

Grist

Grist is a modern relational spreadsheet. It combines the flexibility of a spreadsheet with the robustness of a database.

  • grist-core (this repo – also known as Grist Community edition) has what you need to run a powerful server for hosting spreadsheets.
  • grist-desktop is a Linux/macOS/Windows desktop app for viewing and editing spreadsheets stored locally.
  • grist-static is a fully in-browser build of Grist for displaying spreadsheets on a website without back-end support.

Grist is developed by Grist Labs, an NYC-based company 🇺🇸🗽. The French government 🇫🇷 organizations ANCT Données et Territoires and DINUM (Direction Interministérielle du Numérique) have also made significant contributions to the codebase.

The grist-core, grist-desktop, and grist-static repositories are all open-source (Apache License, Version 2.0). Grist Labs sells an edition of Grist with additional features. Grist Labs also offers free and paid hosted services at getgrist.com,
as well as cloud packaging.

> Questions? Feedback? Want to share what you're building with Grist? Join our official Discord server or visit our Community forum.
>
> To keep up-to-date with everything that's going on, you can sign up for Grist's monthly newsletter.

https://github.com/user-attachments/assets/fe152f60-3d15-4b11-8cb2-05731a90d273

Features in grist-core

To see exactly what is present in grist-core, you can run the desktop app, or use docker. The absolute fastest way to try Grist out is to visit docs.getgrist.com and play with a spreadsheet there immediately – though if you do, please read the list of additional features that are not in grist-core.

However you try it, you'll quickly see that Grist is a hybrid database/spreadsheet, meaning that:

  • Columns work like they do in databases: they are named, and they hold one kind of data.
  • Columns can be filled by formula, spreadsheet-style, with automatic updates when referenced cells change.

This difference can confuse people coming directly from Excel or Google Sheets. Give it a chance! There's also a Grist for Spreadsheet Users article to help get you oriented. If you're coming from Airtable, you'll find the model familiar (and there's also our Grist vs Airtable article for a direct comparison).

Here are some specific feature highlights of Grist (🇫🇷 marks heavy French govt. contributions):

  • Python formulas.
    • Full Python syntax is supported, including the standard library.
    • Many Excel functions also available.
    • An AI Formula Assistant specifically tuned for formula generation (works with OpenAI, Llama, and many other models via OpenRouter or any OpenAI-compatible endpoint).
    • A formula timer for diagnosing slow formulas.
  • A portable, self-contained format.
    • Based on SQLite, the most widely deployed database engine.
    • Any tool that can read SQLite can read numeric and text data from a Grist file.
    • Enables backups that you can confidently restore in full.
    • Great for moving between different hosts.
  • Can be displayed on a static website with grist-static – no special server needed.
  • A self-contained desktop app for viewing and editing locally: grist-desktop.
  • Convenient editing and formatting features.
    • Choices and choice lists, for adding colorful tags to records.
    • References and reference lists, for cross-referencing records in other tables.
    • Two-way references that automatically synchronize between tables.
    • Attachments, to include media or document files in records.
    • Dates and times, toggles, and special numerics such as currency all have specialized editors and formatting options.
    • Conditional Formatting, letting you control the style of cells with formulas to draw attention to important information.
    • Markdown formatting in text cells.
  • Drag-and-drop dashboards.
    • Charts, card views and a calendar widget for visualization.
    • Summary tables for summing and counting across groups.
    • Widget linking streamlines filtering and editing data.
      Grist has a unique approach to visualization, where you can lay out and link distinct widgets to show together,
      without cramming mixed material into a table.
    • Filter bar for quick slicing and dicing.
    • Duplicate widgets to quickly build variations of a view.
    • Compare documents to see what changed.
  • Incremental imports.
    • Import a CSV of the last three months activity from your bank...
    • ...and import new activity a month later without fuss or duplication.
  • Native forms. Create forms that feed directly into your spreadsheet without fuss.
    • Supports file attachments, hidden fields, and pre-population via URL parameters.
  • Integrations.
    • A REST API with an interactive API console, Zapier actions/triggers, and support from similar integrators.
    • Import/export to Google Drive, Excel format, CSV. Import directly from Airtable.
    • Link data with custom widgets, hosted externally.
    • Configurable outgoing webhooks, with support for authorization headers, column-specific triggers, and formula conditions.
    • Service accounts for fine-tuned API access (🇫🇷).
    • SCIM for standard user and group provisioning (🇫🇷).
  • Many templates to get you started, from investment research to organizing treasure hunts.
  • Access control options.
    • (You'll need logins set up to make use of these options — see Logins)
    • Share individual documents, workspaces, or team sites.
    • Control access to individual rows, columns, and tables.
    • Control access based on cell values and user attributes.
  • Collaboration.
    • Comments on cells, with threaded replies and @-mentions.
    • See who else is viewing a document in real time.
    • Suggest changes for others to review and approve, inspired by source control workflows.
  • Self-maintainable.
    • Useful for intranet operation and specific compliance requirements.
    • Sign in with getgrist.com for easy authentication without running your own auth server.
    • Store attachments externally in S3-compatible storage to keep .grist files small (🇫🇷).
    • HTTP long polling as an alternative to WebSockets for restrictive network environments (🇫🇷).
  • Sandboxing options for untrusted documents.
    • On Linux or with Docker, you can enable gVisor sandboxing at the individual document level.
    • On macOS, you can use native sandboxing.
    • On any OS, including Windows, you can use a Wasm-based sandbox via Deno and Pyodide.
  • Translated to many languages (🇫🇷).
  • A high-contrast theme meeting WCAG level AA requirements (🇫🇷).
  • Accessibility support, including screen readers and keyboard navigation across grid views, menus, and the page widget picker (🇫🇷).
  • F1 key brings up some quick help. This used to go without saying, but in general Grist has good keyboard support (🇫🇷).
  • We post progress on 𝕏 or Twitter or whatever and publish monthly newsletters.

If you are curious about where Grist is heading, see our roadmap, drop a question in our forum, or browse our extensive documentation.

Features not in grist-core

If you evaluate Grist by using the hosted version at getgrist.com, be aware that it includes some features that aren't present in grist-core. To be sure you're seeing exactly what is present in grist-core, you can run the desktop app, or use docker.

Here is a list of features available in the full edition of Grist that are not in grist-core, in chronological order of creation. If self-hosting, you can get access to a free trial of all of them by selecting the full edition of Grist on the Admin Panel. The full edition of Grist is free for individuals and small orgs with less than US $1 million in total annual funding. Learn more about that here.

  • GristConnect (2022)
    • Any site that has plugins for letting Discourse use its logins (such as WordPress) can also let Grist use its logins.
    • GristConnect is a niche feature built for a specific client which you probably don't care about.
  • Azure back-end for document storage (2022)
    • With grist-core you can store document versions in anything S3-compatible, which covers a lot of services, but not Azure specifically. The Azure back-end fills that gap.
    • Unless you are a Microsoft shop you probably don't care about this.
  • Audit log streaming (2024)
    • With grist-core a lot of useful information is logged, but not organized specifically with auditing in mind. Audit log streaming supplies that organization, and a UI for setting things up.
    • Enterprises may care about this.
  • Advanced Admin Controls (2025)
    • This is a special page for a Grist installation administrator to monitor and edit user access to resources.
    • It uses a special set of administrative endpoints not present on grist-core.
    • If you're going to be running a large Grist installation, with employees coming and going, you may care about this.
  • Grist Assistant (2025)
    • An AI Formula Assistant - limited to working with formulas - is present in grist-core, but the newer Assistant can help with a wider range of tasks like building tables and dashboards, styling and formatting, explaining access rules, and modifying data.
    • If you have many users who need help building documents or working with data, you may care about this one.
  • Invite Notifications (2025)
    • When a user is added to a document, or a workspace, or a site, with email notifications they will get emailed a link to access the resource.
    • This link isn't special, with grist-core you can just send a link yourself or a colleague.
    • For a big Grist installation with users who aren't in close communication, emails might be nice? Hard to guess if you'll care about this one.
  • Document Change and Comment Notifications (2025)
    • You can achieve change notifications in grist-core using webhooks, but it is less convenient.
    • People have been asking for this one for years. If you need an excuse to get your boss to pay for Grist, this might finally be the one that works?
  • Automations (2026)
    • A tool for document owners to build trigger-driven workflows: set conditions on any table, then send emails (with dynamic recipients and Markdown) or fire webhooks when rows match, and watch the results in a delivery log.
    • You can build similar flows in grist-core with webhooks, but you'd be wiring up the email side and the monitoring yourself.
  • OAuth apps (2026)
    • Register and authorize OAuth applications, scope them to specific orgs, workspaces, or documents, and review or revoke that access later.
    • A way to give external tools connection to Grist with scoped, revocable access instead of handing over a full API key. If you're connecting Grist to other software, you may care about this, as an alternative to API keys.
  • MCP server (2026)
    • A built-in Model Context Protocol endpoint that lets AI clients such as Claude or ChatGPT read and edit Grist documents over JSON-RPC. Enabled with GRIST_MCP_ENABLED (see environment variables).
    • With grist-core you can still use one of the many community MCP servers that talks to Grist through its REST API. The built-in server saves you that work.
  • Single sign-on (SSO) via OIDC or SAML (2026)

Using Grist

To get the default version of grist-core running on your computer
with Docker, do:```sh
docker pull gristlabs/grist
docker run -p 8484:8484 -it gristlabs/grist


Then visit `http://localhost:8484` in your browser.

On a brand new install you'll land on a **Quick setup** page that walks
you through choosing an admin email, picking how people sign in, and
setting who can use the site. To get past the first screen, look in the
container's startup log for a line containing a generated boot key, and
paste it in when prompted. Once you click **Apply and go live!** at the
end of Quick setup, the site is open for business and you'll be able to
create, edit, import, and export documents. There's a step-by-step
walkthrough at
First-run setup.

If you'd rather skip Quick setup entirely and start with an open,
single-user setup, set `GRIST_IN_SERVICE=true`. You can come back to
the same settings later from the Admin Panel.

To preserve your work across docker runs, share a directory as `/persist`:```sh
docker run -p 8484:8484 -v $PWD/persist:/persist -it gristlabs/grist

Get templates at templates.getgrist.com for payroll,
inventory management, invoicing, D&D encounter tracking, and a lot
more, or use any document you've created on
docs.getgrist.com.

If you need to change the port Grist runs on, set a PORT variable, don't just change the
port mapping:```
docker run --env PORT=9999 -p 9999:9999 -v $PWD/persist:/persist -it gristlabs/grist


To enable gVisor sandboxing, set `--env GRIST_SANDBOX_FLAVOR=gvisor`.
This should work with default docker settings, but may not work in all
environments.

You can find a lot more about configuring Grist, setting up authentication,
and running it on a public server in our
Self-Managed Grist documentation.

## Using Grist with OpenRouter for Model Agnostic and Claude Support

(Instructions contributed by @lshalon)

Grist's AI Formula Assistant can be configured to use OpenRouter instead of connecting directly to OpenAI, allowing you to access a wide range of AI models including Anthropic's Claude models. This isn't the only way to use Claude models, but it's a good option if you want to use Claude models with Grist or intend to use other cheaper, faster, or potentially newer models. That's because this configuration gives you more flexibility in choosing the AI model that works best for your formula generation needs.
To set up OpenRouter integration, configure the following environment variables:

### Required: Set the endpoint to OpenRouter's API```
ASSISTANT_CHAT_COMPLETION_ENDPOINT=https://openrouter.ai/api/v1/chat/completions

Required: Your OpenRouter API key```

ASSISTANT_API_KEY=your_openrouter_api_key_here


Sign up for an OpenRouter API key at

### Optional: Specify which model to use (examples below)```
ASSISTANT_MODEL=anthropic/claude-3.7-sonnet

or other options like```

ASSISTANT_MODEL=deepseek/deepseek-r1-zero:free

ASSISTANT_MODEL=qwen/qwq-32b:free

ASSISTANT_MODEL=mistralai/mistral-saba


### Optional: Set a larger context model for fallback```
ASSISTANT_LONGER_CONTEXT_MODEL=anthropic/claude-3-opus-20240229

With this configuration, Grist's AI Formula Assistant will route requests through OpenRouter to your specified model. This allows you to:

Access Anthropic's Claude models which excel at understanding context and generating accurate formulas
Switch between different AI models without changing your Grist configuration
Take advantage of OpenRouter's routing capabilities to optimize for cost, speed, or quality

You can find the available models and their identifiers on the OpenRouter website.
Note: Make sure not to set the OPENAI_API_KEY variable when using OpenRouter, as this would override the OpenRouter configuration.

Available Docker images

The default Docker image is gristlabs/grist. This contains all of
the Grist Community edition features, as well as extra extensions for the full edition of Grist. These
extensions are not under a free or open-source license. These extensions becomes active only when
the edition in the Admin Panel is set to "Full Grist", and are inert and inactive when it is set
to "Community Grist".

If you would rather use an image that contains exclusively free and
open-source code, the gristlabs/grist-oss Docker image is available
for this purpose. It is functionally equivalent to the
gristlabs/grist image whose edition is set to "Community Grist".

The Admin Panel

The Admin Panel is where you inspect and tweak your installation:
check health probes, change a few settings, toggle features. Visit
/admin on your Grist server to find it. If you're not yet signed in
as the installation admin, the panel will prompt you to do a boot key
login, and from there you can paste in the key.

New installs generate a boot key automatically and print it to the
container log on startup. Watch for a line like:```
BOOT KEY: <random-string>


If you&#x27;d rather pick your own boot key, set `GRIST_BOOT_KEY`:```
docker run -p 8484:8484 -e GRIST_BOOT_KEY=secret -it gristlabs/grist

The panel collects probes for common problems. If you hit one that
isn't covered, please add a probe in
BootProbes,
or file an issue so someone else can.

Building from source

To build Grist from source, follow these steps:

yarn install
yarn install:python
yarn build
yarn start
# Grist will be available at http://localhost:8484/

By default, the build is the full edition: yarn install downloads optional
extensions (into an ext directory) that are only enabled when switching to the full
edition of Grist from the Admin Panel.
Note that this will add non-OSS code to your build.

If you wish to skip including extensions in your build, the steps are as follows:

yarn run set-community-edition
yarn install:python
yarn build
yarn start
# Grist will be available at http://localhost:8484/

You may toggle between the full Grist and Community editions in the Admin Panel.

The first time you start Grist it'll show the Quick setup page, just
like a fresh Docker install. Look at the terminal where you ran
yarn start for the boot key. If you'd rather skip Quick setup while
hacking, run with GRIST_IN_SERVICE=true.

Grist formulas in documents will be run using Python executed directly on your
machine. You can configure sandboxing using a GRIST_SANDBOX_FLAVOR
environment variable.

  • On macOS, export GRIST_SANDBOX_FLAVOR=macSandboxExec
    uses the native sandbox-exec command for sandboxing.
  • On Linux with gVisor's runsc
    installed, export GRIST_SANDBOX_FLAVOR=gvisor is an option.
  • On any OS including Windows, export GRIST_SANDBOX_FLAVOR=pyodide is available.

These sandboxing methods have been written for our own use at Grist Labs and
may need tweaking to work in your own environment - pull requests
very welcome here!

Logins

Like git, Grist has features to track document revision history. So for full operation,
Grist expects to know who the user modifying a document is. Until it does, it operates
in a limited anonymous mode.

The friendliest way to get sign-in set up is the Quick setup page that
appears on a fresh install. It lets you pick an admin email and an
authentication method from a short menu. See
First-run setup
for the full walkthrough. You can revisit those same settings later
from the Admin Panel.

If you'd rather not configure sign-in at all, you can run with a single
default identity. Set GRIST_DEFAULT_EMAIL and the "sign in" button
will attribute your work to that address:docker run --env GRIST_DEFAULT_EMAIL=my@email -p 8484:8484 -v $PWD/persist:/persist -it gristlabs/grist

You can change your name in Profile Settings in
the User Menu.

For multi-user operation, or if you wish to access Grist across the
public internet, you'll want to connect it to a Single Sign-On service.
Sign in with getgrist.com
and forward authentication
are available in all editions; connecting directly to your own identity
provider via OIDC or
SAML is
fully supported with an activation key.
Grist has been tested with Authentik, Auth0,
and Google/Microsoft sign-ins via Dex.

Thanks to everyone who is pitching in. Thanks especially to the ANCT developers who
did the hard work of making a good chunk of the application localizable. Merci beaucoup !

Why free and open-source software?

This repository, grist-core, is maintained by Grist Labs. Our flagship product available at getgrist.com is built from the code you see here, combined with business-specific software designed to scale to many users, handle billing, etc.

Grist Labs is an open-core company. We offer Grist hosting as a service, with free and paid plans. We also develop and sell features related to Grist using a proprietary license, targeted at the needs of enterprises with large self-managed installations.

We see data portability and autonomy as a key value, and grist-core is an essential part of that. We are committed to maintaining and improving the grist-core codebase, and to be thoughtful about how proprietary offerings impact data portability and autonomy.

By opening its source code and offering an OSI-approved free license, Grist benefits its users:

  • Developer community. The freedom to examine source code, make bug fixes, and develop
    new features is a big deal for a general-purpose spreadsheet-like product, where there is a
    very long tail of features vital to someone somewhere.
  • Increased trust. Because anyone can examine the source code, “security by obscurity” is not
    an option. Vulnerabilities in the code can be found by others and reported before they cause
    damage.
  • Independence. Grist is available to you regardless of the fortunes of the Grist Labs business,
    since it is open-source and can be self-hosted. Using our hosted solution is convenient, but you
    are not locked in.
  • Price flexibility. If you are low on funds but have time to invest, self-hosting is a great
    option to have. And DIY users may have the technical savvy and motivation to delve in and make improvements,
    which can benefit all users of Grist.
  • Extensibility. For developers, having the source open makes it easier to build extensions (such as Custom Widgets). You can more easily include Grist in your pipeline. And if a feature is missing, you can just take the source code and build on top of it.

For more on Grist Labs' history and principles, see our About Us page.

Sponsors

Reviews

  • Grist on ProductHunt
  • Grist on AppSumo (life-time deal is sold out)
  • Capterra, G2, TrustRadius

Environment variables

Grist can be configured in many ways. Here are the main environment variables it is sensitive to:

Variable Purpose
ALLOWED_WEBHOOK_DOMAINS comma-separated list of permitted domains to use in webhooks (e.g. webhook.site,zapier.com). You can set this to * to allow all domains, but if doing so, we recommend using a carefully locked-down proxy (see GRIST_PROXY_FOR_UNTRUSTED_URLS) if you do not entirely trust users. Otherwise services on your internal network may become vulnerable to manipulation.
APP_DOC_URL the url a browser should use to reach this doc worker. In a multi-server setup, if not using GRIST_FLEET, every doc worker must be reachable by the browser at a public url of its own. If not using GRIST_ROUTER_URL to assign those automatically, APP_DOC_URL needs setting in practice. Wherever it is set it must be distinct for each worker, since it is how a client reaches the worker holding a document, and, where APP_DOC_INTERNAL_URL is unset, how other servers reach it too. Behind a single front end that means a path per worker, such as https://grist.example.com/dw/worker-1. Setting it alongside GRIST_FLEET is refused at startup, since a fleet routes clients through whichever server they reach and never uses it.
APP_DOC_INTERNAL_URL like APP_DOC_URL but used by other servers to reach this one using an internal domain name resolution (like in a docker environment). It only makes sense to define this value in the doc worker. Defaults to APP_DOC_URL. If both are unset, an address is derived from GRIST_HOST, or from the interface this server reaches Redis on. Workers that share a host can be told apart by path, and the id derived from this url includes it.
APP_HOME_URL url prefix for home api (home and doc servers need this)
APP_HOME_INTERNAL_URL like APP_HOME_URL but used by the home and the doc servers to reach any home workers using an internal domain name resolution (like in a docker environment). Defaults to APP_HOME_URL
APP_STATIC_URL url prefix for static resources
APP_STATIC_INCLUDE_CUSTOM_CSS set to "true" to include custom.css (from APP_STATIC_URL) in static pages
APP_UNTRUSTED_URL URL at which to serve/expect plugin content.
GRIST_ACTION_HISTORY_MAX_ROWS Maximum number of rows allowed in ActionHistory before pruning (up to a 1.25 grace factor). Defaults to 1000. ⚠️ A too low value may make the "Work on a copy" feature malfunction
GRIST_ACTION_HISTORY_MAX_BYTES Maximum number of rows allowed in ActionHistory before pruning (up to a 1.25 grace factor). Defaults to 1Gb. ⚠️ A too low value may make the "Work on a copy" feature malfunction
GRIST_ADAPT_DOMAIN set to "true" to support multiple base domains (careful, host header should be trustworthy)
GRIST_ALLOW_AUTOMATIC_VERSION_CHECKING Whether Grist is allowed to automatically check if a newer Grist version is available. Defaults to "true" on the default grist and grist-ee Docker images. Defaults false in grist-oss and everywhere else.
GRIST_ALLOW_DEPRECATED_BARE_ORG_DELETE If set, the deprecated DELETE /api/orgs/:orgId endpoint is available.
GRIST_APP_ROOT directory containing Grist sandbox and assets (specifically the sandbox and static subdirectories).
GRIST_ATTACHMENTS_THRESHOLD_MB attachment storage limit per document beyond which Grist will recommend external storage (if available). Defaults to 50MB.
GRIST_BACKUP_DELAY_SECS wait this long after a doc change before making a backup
GRIST_BOOT_KEY if set, use this key to sign in as the installation admin at /boot. New installs auto-generate one and print it on startup; set this only if you want a key of your own choosing.
GRIST_BROADCAST_TIMEOUT_MS Set the maximum time a web client has to accept a broadcast message about a document before being disconnected (default: 1 minute).
GRIST_DATA_DIR Directory in which to store documents. Defaults to docs/ relative to the Grist application directory. In Grist's default Docker image, its default value is /persist/docs so that it will be used as a mounted volume.
GRIST_DEFAULT_EMAIL if set, login as this user if no other credentials presented
GRIST_DEFAULT_PRODUCT if set, this controls enabled features and limits of new sites. See names of PRODUCTS in Product.ts.
GRIST_DEFAULT_LOCALE Locale to use as fallback when Grist cannot honour the browser locale. Defaults to en-US. Should match a locale code found in app/common/LocaleCodes.ts.
GRIST_DOC_WORKER_ID identity of a doc worker, which must be distinct for every server sharing a Redis. Leave it unset to have one derived. Two servers sharing a value can open the same document at once.
GRIST_DOMAIN in hosted Grist, Grist is served from subdomains of this domain. Defaults to "getgrist.com".
GRIST_EDITION selects which edition the yarn install hook sets up, full or community. Takes precedence over the grist-edition file written by yarn run set-full-edition / yarn run set-community-edition. Defaults to full. See Building from source.
GRIST_SKIP_EXT_AUTOSETUP set to 1 to skip the yarn install hook that downloads the full-edition ext material. Useful where extensions are installed by other means (Docker builds, grist-desktop, grist-static). See Building from source.
GRIST_EXPERIMENTAL_PLUGINS enables experimental plugins
GRIST_EXTERNAL_ATTACHMENTS_MODE required to enable external storage for attachments. Set to "snapshots" to enable external storage. Default value is "none". Note that when enabled, a snapshot storage has to be configured as well.
GRIST_ENABLE_SERVICE_ACCOUNTS enables the service accounts feature. This feature allows users to create special service accounts that they can manage and to whom they can grant restricted access to chosen resources. Useful as a way to get fine-grained api keys for use with third party automations. Unset by default
GRIST_ENABLE_REQUEST_FUNCTION enables the REQUEST function. This function performs HTTP requests in a similar way to requests.request. This function presents a significant security risk, since it can let users call internal endpoints when Grist is available publicly. This function can also cause performance issues. Unset by default.
GRIST_HEADERS_TIMEOUT_MS if set, override nodes's server.headersTimeout flag.
GRIST_HIDE_UI_ELEMENTS comma-separated list of UI features to disable. Allowed names of parts: helpCenter, billing, templates, createSite, multiSite, multiAccounts, importFromAirtable, sendToDrive, tutorials, supportGrist, themes, automations. If a part also exists in GRIST_UI_FEATURES, it will still be disabled.
GRIST_HOST hostname to use when listening on a port. Also decides the address a doc worker publishes for its peers, and the identity derived from it: set it to 0.0.0.0 to listen on every interface, and leave it unset to listen only on localhost.
GRIST_PROXY_FOR_UNTRUSTED_URLS Full URL of proxy for delivering webhook payloads. Default value is direct for delivering payloads without proxying.
HTTPS_PROXY or https_proxy Full URL of reverse web proxy (corporate proxy) for fetching the custom widgets repository or the OIDC config from the issuer.
GRIST_ID_PREFIX for subdomains of form o-, expect or produce o-${GRIST_ID_PREFIX}.
GRIST_IGNORE_SESSION if set, Grist will not use a session for authentication.
GRIST_INCLUDE_CUSTOM_SCRIPT_URL if set, will load the referenced URL in a `` tag on all app pages.
GRIST_IN_SERVICE if "true", skip the first-run Quick setup gate and put the server straight into service. New installs default to "false" so the operator can finish Quick setup; existing installs default to "true".
GRIST_INST_DIR path to Grist instance configuration files, for Grist server.

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Grist 怎么安装?

在客户端按下面的安装命令接入:https://docs.getgrist.com/api/mcp。装完在客户端配置里引用同一个包或端点。

Grist 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Grist 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Grist 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Grist 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Grist 能提供哪些能力?

资料显示能力标签包括 spreadsheet、database、no code、productivity、oauth、remote。具体工具清单以官方文档为准。

Grist 需要什么运行环境?

运行时为 Cross-platform;属于远程端点,不需要在本地装运行时。

Grist 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。