Record MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| R2_ACCOUNT_ID | No | Your Cloudflare R2 account ID (required when STORAGE_PROVIDER=r2) | |
| R2_BUCKET_NAME | No | Your Cloudflare R2 bucket name (required when STORAGE_PROVIDER=r2) | |
| LOCAL_DATA_PATH | No | Path for local file storage (used when STORAGE_PROVIDER=local) | ./data |
| R2_ACCESS_KEY_ID | No | Your Cloudflare R2 access key ID (required when STORAGE_PROVIDER=r2) | |
| STORAGE_PROVIDER | No | The storage provider to use (local or r2) | local |
| R2_SECRET_ACCESS_KEY | No | Your Cloudflare R2 secret access key (required when STORAGE_PROVIDER=r2) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_review_typesB | List all review types with their schemas and record counts |
| get_review_typeC | Get detailed information about a specific review type including all records |
| add_review_typeC | Create a new review type with a custom schema |
| add_field_to_typeB | Add a new field to an existing review type schema |
| add_review_recordC | Add a new review record to a type |
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 5 tools
Each tool has a clearly distinct purpose: add_field_to_type modifies schemas, add_review_record creates data entries, add_review_type creates new types, get_review_type retrieves detailed type information, and list_review_types provides an overview. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern (e.g., add_field_to_type, get_review_type, list_review_types) with clear, descriptive actions and targets. The naming is uniform and predictable throughout the set.
With 5 tools, this server is well-scoped for managing review types and records. The count is appropriate, covering core operations without being overly sparse or bloated, and each tool serves a necessary function in the domain.
The tool set provides good coverage for creating and retrieving review types and records, but lacks update and delete operations (e.g., update_review_type, delete_review_record). This minor gap might require workarounds but does not severely hinder core workflows.