io.github.CloudCorpRecords/gridbase
Bases, tables, and records in Airtable: list, search, create, update, delete.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@reneturcios/gridbaseclaude mcp add gridbase -- npx -y @reneturcios/gridbase@0.1.0 mcp
{
"mcpServers": {
"gridbase": {
"command": "npx",
"args": [
"-y",
"@reneturcios/gridbase@0.1.0",
"mcp"
]
}
}
}
ghcr.io/cloudcorprecords/gridbase:0.1.0claude mcp add gridbase -- docker run -i --rm ghcr.io/cloudcorprecords/gridbase:0.1.0 mcp
{
"mcpServers": {
"gridbase": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cloudcorprecords/gridbase:0.1.0",
"mcp"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
gridbase
gridbase is a workbench for Airtable. It walks a base the way a person would: first the list of bases a token can reach, then the tables inside one base and the fields and views each table declares, then the records themselves — listed, filtered by formula, searched by text, or fetched one at a time. The same surface writes back: records can be created, updated, and deleted, tables and fields can be created and renamed, and comments can be attached to records and read again. One binary serves a command-line interface and a stdio MCP server.
An Airtable personal access token is required. Put it in the
AIRTABLE_API_KEY environment variable; it is sent to the API as an
Authorization: Bearer header and never appears in output. When the
variable is missing, every call fails with an error that names it,
before any request is made. The token needs the schema.bases:read
and data.records:read scopes at minimum, plus the matching write
scopes for the write tools.
Install
npx @reneturcios/gridbase bases
Or run the container image:
docker run -i -e AIRTABLE_API_KEY ghcr.io/cloudcorprecords/gridbase
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
CLI
export AIRTABLE_API_KEY="pat..."
gridbase bases
gridbase tables appXXXXXXXXXXXXXX --detail full
gridbase describe appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX
gridbase records appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX --max 25 --filter "{Status}='Open'"
gridbase search appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX "quarterly report"
gridbase get appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX recXXXXXXXXXXXXXX
gridbase create appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX '{"Name":"New task","Status":"Open"}'
gridbase update appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX '[{"id":"recXXXXXXXXXXXXXX","fields":{"Status":"Done"}}]'
gridbase delete appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX recXXXXXXXXXXXXXX
gridbase create-table appXXXXXXXXXXXXXX Reports '[{"name":"Title","type":"singleLineText"}]'
gridbase comment appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX recXXXXXXXXXXXXXX "Looks good"
gridbase comments appXXXXXXXXXXXXXX tblXXXXXXXXXXXXXX recXXXXXXXXXXXXXX --page-size 10
gridbase --version
Each command prints the upstream JSON payload. Exit codes: 0 on
success, 1 when a call fails (including a missing AIRTABLE_API_KEY
or an API error), 2 for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/gridbase mcp
MCP client configuration:
{
"mcpServers": {
"gridbase": {
"command": "npx",
"args": ["-y", "@reneturcios/gridbase", "mcp"],
"env": { "AIRTABLE_API_KEY": "pat..." }
}
}
}
Tools
| Tool | Input | What it returns |
|---|---|---|
list_bases | (none) | Every accessible base with its ID, name, and permission level. |
list_tables | baseId (required), detailLevel (optional) | Tables in the base, trimmed to the requested detail level. |
describe_table | baseId, tableId (required), detailLevel (optional) | One table's fields and views. |
list_records | baseId, tableId (required), maxRecords, filterByFormula (optional) | Records from the table. |
search_records | baseId, tableId, searchTerm (required), fieldIds, maxRecords (optional) | Records whose field values contain the term. |
get_record | baseId, tableId, recordId (required) | The single record. |
create_record | baseId, tableId, fields (required) | The created record. |
update_records | baseId, tableId, records (required) | The updated records. |
delete_records | baseId, tableId, recordIds (required) | Deletion receipts for each record. |
create_table | baseId, name, fields (required), description (optional) | The created table. |
update_table | baseId, tableId (required), name, description (optional) | The updated table. |
create_field | baseId, tableId, name, type (required), description, options (optional) | The created field. |
update_field | baseId, tableId, fieldId (required), name, description (optional) | The updated field. |
create_comment | baseId, tableId, recordId, text (required), parentCommentId (optional) | The created comment. |
list_comments | baseId, tableId, recordId (required), pageSize, offset (optional) | The record's comments, newest first. |
Airtable offers no text-search endpoint, so search_records lists
the table (bounded by maxRecords) and keeps the records whose field
values contain the term, restricted to fieldIds when supplied.
Schema reads trim the meta payload themselves: tableIdentifiersOnly
keeps table IDs and names, identifiersOnly also reduces fields and
views to IDs and names, and full (the default) returns everything.
Development
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)
npm run dev # run the CLI from source via tsx
License
MIT — see LICENSE.
Questions fréquentes
Qu'est-ce que io.github.CloudCorpRecords/gridbase ?
Bases, tables, and records in Airtable: list, search, create, update, delete.
Comment installer io.github.CloudCorpRecords/gridbase ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add gridbase -- npx -y @reneturcios/gridbase@0.1.0 mcp. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.CloudCorpRecords/gridbase ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.CloudCorpRecords/gridbase est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.CloudCorpRecords/gridbase ?
Il est publié par CloudCorpRecords. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.