Shoanta MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOANTA_API_URL | Yes | Shoanta base URL, e.g. https://shoanta.jullury.com | |
| SHOANTA_API_TOKEN | Yes | API token created in Workspace Settings → API tokens |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_collectionsA | List all collections (databases) in the Shoanta workspace. |
| list_documentsA | List all documents in a collection. |
| get_documentA | Get a single document by ID, including its property values. |
| create_documentC | Create a new document in a collection. |
| update_documentA | Update document title, content, and/or property values. Only provided fields are changed. |
| delete_documentA | Delete a document. If archive is true, it is moved to trash instead of being permanently deleted. |
| list_commentsB | List comments on a document. |
| add_commentB | Add a comment to a document. |
| list_propertiesA | List all property (column) definitions for a collection. |
| add_propertyB | Add a new property (column) to a collection. Type one of TEXT, NUMBER, SELECT, MULTI_SELECT, DATE, CHECKBOX, URL, FORMULA, RELATION (default TEXT). For SELECT/MULTI_SELECT, pass options as [{value, color?}]. |
| delete_propertyA | Delete a property (column) from a collection by name. Removes the column and all its values. |
| transfer_collectionA | Transfer a collection (and its documents) to another workspace. The API token's user must be a member of the target workspace. Provide the target workspace slug. |
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 12 tools
Each tool maps to a distinct resource+action pair: document CRUD, comment list/add, property list/add/delete, and collection listing/transferring are all clearly separated. There is no case where two tools could plausibly be selected for the same request, since naming and descriptions both encode the target resource explicitly.
All twelve tools follow a strict snake_case verb_noun pattern (get_document, list_properties, add_property, delete_document, transfer_collection). The verb choices are semantically appropriate and consistently applied to each resource, with no camelCase or stylistic drift.
Twelve tools sit squarely in the well-scoped range for a document-database server. Each tool covers a distinct operation (read, list, create, update, delete across documents, properties, comments, collections) with no filler or redundant entries.
Documents have full CRUD coverage, but properties only support list/add/delete with no update_property (no renaming or changing select options), comments lack any delete or update operation, and collections can only be listed or transferred — there is no create_collection or delete_collection. These are notable gaps that could force workarounds in common admin workflows.