trinitas-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRINITAS_DATA_DIR | No | Base directory for local data | data |
| TRINITAS_MEMORY_DB | No | SQLite memory path | {TRINITAS_DATA_DIR}/trinitas_memory.db |
| PROVIDER_REGISTRY_URL | No | Registry document URL | GitHub Pages registry.json |
| PROVIDER_REGISTRY_BASE | No | Registry base for future detail fetches | GitHub Pages base URL |
| REGISTRY_CACHE_TTL_SECONDS | No | In-memory registry cache TTL | 60 |
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 |
|---|---|
| store_dialog_turnA | Store a single dialog turn in persistent session memory. Persists a message (user, assistant, system, or tool) for later retrieval and context assembly. Metadata can hold arbitrary JSON-serializable context such as model name, tool calls, or review state. Args:
session_id: Unique conversation session identifier.
role: Speaker role (e.g. Returns: JSON string with the stored turn record including assigned id. |
| retrieve_recent_contextA | Retrieve the most recent dialog turns for a session. Returns turns in chronological order (oldest first) so they can be directly used as LLM context. Args: session_id: Conversation session to query. limit: Maximum number of recent turns to return (default 10). Returns: JSON string with session id, turn count, and turn list. |
| search_memoryA | Search dialog memory within a session by text substring. Performs a case-insensitive LIKE search over turn content and roles. Suitable for finding earlier mentions of topics, decisions, or entities. Args: session_id: Conversation session to search. query: Substring to match in content or role. limit: Maximum results to return (default 20). Returns: JSON string with matching turns, newest first. |
| route_best_modelA | Recommend the best AI provider for a given task type. Uses the public Args:
task_type: Task category — Returns: JSON string with top recommendation and up to four alternatives. |
| list_available_providersA | List all providers from the AI Provider Registry. Fetches the live registry document and returns provider summaries including id, api_style, free-tier status, and supported capabilities. Returns: JSON string with registry metadata and provider list. |
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: list providers, retrieve recent dialog, route best model, search memory, and store dialog turn. No overlapping functionality.
All tool names follow the verb_noun pattern in snake_case (e.g., list_available_providers, store_dialog_turn), providing a predictable and consistent naming scheme.
5 tools is on the lower side but acceptable for a server combining provider routing and dialog memory. Each tool serves a clear role without redundancy.
Dialog memory covers store, retrieve, and search adequately. Provider coverage has list and route but lacks a single-provider detail lookup, a minor gap.