Testimonial.to MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TESTIMONIAL_API_KEY | No | One private Space Bearer key; do not combine with token file. Configure exactly one of TESTIMONIAL_API_KEY or TESTIMONIAL_TOKEN_FILE in the private process settings. The client sends Authorization: Bearer; do not include the word Bearer in the value. | |
| TESTIMONIAL_ACCOUNTS | No | Private JSON array of unique name/api_key/token_file profiles; no fallback. Configure one credential source per profile. | |
| TESTIMONIAL_AUDIT_LOG | No | Optional private append-only guard decisions log path. | |
| TESTIMONIAL_READ_ONLY | No | 1/true hides and refuses effects (hides the five write/file tools and refuses direct hidden calls). | |
| TESTIMONIAL_TOKEN_FILE | No | Absolute owner-only token-only file, maximum 64 KiB; cached until restart. Token files must be absolute, regular, non-symlink, token-only files outside repositories. On macOS/Linux the file must be owned by your runtime user and mode 0600. | |
| TESTIMONIAL_DEFAULT_ACCOUNT | No | Exact private profile label selected as the default account. | |
| TESTIMONIAL_ALLOW_DESTRUCTIVE | No | 0/false refuses confirmed effects too. | |
| TESTIMONIAL_REQUEST_TIMEOUT_MS | No | 100-300000, default 30000 ms; no retry. | |
| TESTIMONIAL_MIN_REQUEST_INTERVAL_MS | No | 0-10000, default 250 ms; local spacing, not quota. |
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_testimonialsB | Read one native JSON array. Only ready video assets are included; no page, cursor or offset parameters. |
| verify_spaceC | Explicit native key verification. Response includes Space id and account email; private metadata, not ownership or all-action proof. |
| submit_text_testimonialA | Import a real authorized customer statement. Local confirm approves the API call; customer_consent or payload.confirm represents actual public-use permission. |
| submit_video_testimonialA | Import a real publicly accessible authorized video. Provider retrieves/processes the URL; this package never downloads it. Success does not mean processing finished. |
| send_testimonial_requestA | Side-effecting GET sends a real request email. Explicit local confirmation is mandatory. No dry run, retry or delivery guarantee. |
| list_accountsB | Local profile labels/default/auth method only. No keys, token paths, provider identity or network request. |
| get_operation_schemaA | Local reviewed method/path/query/body schema and provenance for one native tool. No credentials or provider request. |
| preview_testimonial_batchA | Local validation and SHA-256 of exact ordered text/video import/email work, selected profile label and reviewed schema. No provider reads, key load, identity check, price or rollback guarantee. |
| submit_testimonial_batchA | Confirmed one-to-twenty ordered text/video import/email tasks. Prevalidate all and verify exact hash before first request. Stop on first failure with known results/failed index/unattempted indices; no retries, rollback or implicit continuation. |
| export_testimonialsA | Confirmed single native GET saved to a new exclusive mode 0600 JSON file, default limit 100/local maximum 10,000 and 5 MiB response/file cap. No pagination, continuation, media download, overwrite or atomic complete-backup claim. |
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 10 tools
Most tools have clearly distinct purposes (schema lookup, account listing, verification, listing, exporting, requesting, single vs batch import). The main risk is overlap between submit_text_testimonial/submit_video_testimonial/submit_testimonial_batch and between list_testimonials/export_testimonials, but the detailed descriptions clarify the boundaries.
All tools follow a consistent snake_case verb_noun convention (get_operation_schema, list_accounts, submit_text_testimonial, export_testimonials, verify_space). No mixing of camelCase or inconsistent verb styles.
Ten tools is well-scoped for a testimonial platform integration, covering auth, discovery, listing, exporting, and several import/request paths. Each tool appears to earn its place.
Core read and import workflows (list, export, submit text/video/batch, request) are covered, but there are notable gaps: no update or delete for testimonials and no get-single-testimonial operation. This leaves lifecycle management incomplete for a CRUD-style domain.