teralynk-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERALYNK_API_KEY | Yes | Your Teralynk API key (get at teralynk.com/developer) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesA | List the authenticated user's files in Teralynk. Supports search, pagination, and filtering by storage provider. Returns file IDs needed for scan_file_for_pii, get_file, delete_files, protect_files, and share_file. |
| search_filesB | Full-text search across file names and metadata. Returns ranked results with file IDs. |
| get_fileA | Get full metadata for a specific file: name, size, type, storage provider, tags, created/modified dates, compliance protection status, and a 15-minute presigned download URL. |
| get_file_download_urlB | Get a presigned download URL for a file. URL is valid for 15 minutes. |
| get_file_versionsA | List all versions of a file with timestamps and sizes. Useful before deciding to delete or restore. |
| get_compliance_scoreA | Get the user's real-time compliance health score (0–100) with a breakdown by framework. Score reflects open violations, scan coverage, and policy adherence. A score ≥ 85 is typically considered compliant for enterprise audits. |
| get_analyticsA | Get usage analytics: file count, total storage used, AI query count, active workflows, and compliance scan statistics. Use get_storage_analytics for storage-specific breakdowns. |
| list_conversationsB | List previous AI chat conversations with title, last message preview, model used, and timestamps. |
| get_job_statusA | Check the status of a long-running async operation — full compliance scan, report generation, or DSAR. Poll until status is "completed" or "failed". Returns progress percentage and result location when done. |
| get_conversationA | Get a specific AI chat conversation by ID, including full message history. Useful for resuming context. |
| get_billing_usageA | Get the current billing period usage: plan name, credits remaining, scans used, storage consumed, and renewal date. |
| get_notificationsA | Get the user's recent notifications — file shares, scan completions, violation alerts, workflow updates, and system messages. Returns up to 20 most recent notifications. |
| list_frameworksA | List all available compliance frameworks (HIPAA, GDPR, PCI-DSS, etc.) with descriptions, control counts, and your current coverage percentage. |
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 13 tools
Each tool targets a distinct area: file management, compliance, analytics, conversations, billing, notifications, and job status. There is no overlap in purposes despite some related functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_files, get_file_download_url), with no mixing of conventions or ambiguous verbs.
With 13 tools, the server is well-scoped for a compliance-focused file management platform. Each tool serves a clear purpose without unnecessary bloat or insufficiency.
The set lacks critical tools implied by descriptions: no create/upload file, no delete file, no protect file, no start scan trigger. Agents hitting these gaps will fail, as the domain expects CRUD and compliance actions.