ragic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAGIC_SERVER | Yes | The Ragic server domain (e.g., ap5.ragic.com, www.ragic.com, na3.ragic.com, eu2.ragic.com) | |
| RAGIC_ACCOUNT | Yes | Your Ragic account name (found in the URL after the server) | |
| RAGIC_API_KEY | Yes | Your Ragic API key from account settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ragic_list_sheetsA | List every sheet the configured API key can see, grouped by tab. Returns a tree: account -> tabs (path like "/sales") -> sheets (key = sheet_index, value = {name, type, seq}). Use this as the FIRST call when the user asks about a sheet by Chinese name — find it in the tree, then use the matching path & sheet_index for subsequent tools. No arguments. The user doesn't need to paste a URL anymore. |
| ragic_list_recordsA | Read records from a Ragic sheet.
Call ragic_filter_help() for the full cheatsheet including system field IDs. |
| ragic_get_recordB | Read one record by its Ragic node id ( |
| ragic_searchC | Full-text search a sheet (Ragic |
| ragic_create_recordB | Create a new record. For subtables include Requires an API key with write permission; otherwise Ragic returns 401. |
| ragic_update_recordB | Update fields of an existing record. Only the provided fields change.
|
| ragic_delete_recordB | Delete a record. Ragic does not support batch delete via this endpoint. |
| ragic_approveB | Approve or reject a record awaiting approval.
|
| ragic_lockC | Lock a record to prevent further edits. |
| ragic_unlockC | Unlock a previously locked record. |
| ragic_filter_helpA | Return the Ragic filter / write-parameter cheatsheet. Read this once at the start of a Ragic task to understand the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct operation (CRUD, search, list sheets, lock/unlock, approve, filter help) with no overlap. An agent can easily distinguish them.
All tool names follow a consistent `ragic_verb_noun` pattern (e.g., ragic_create_record, ragic_list_sheets). No mixing of conventions.
With 11 tools, the set is well-scoped for a database client, covering essential operations without superfluous tools.
The tools provide full CRUD, search, sheet discovery, locking, and approval—covering the core Ragic workflow. No obvious gaps for the intended purpose.