suplagentics-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| suplagentics_import_scanA | Scans this machine for opencode session history (from opencode.db) and Claude Code session history (from ~/.claude/projects/) that has not yet been imported into opencode-mem. Returns real per-project session/memory counts and import status — the same data the SuplAgentics dashboard's own Import History page shows. |
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 1 tool
With only one tool, there is no possibility of overlap or confusion; its purpose is singular and clearly stated.
The single tool follows a clear verb_noun pattern (import_scan) with a consistent namespace prefix, and there are no other tools to create inconsistency.
A single tool is too thin for a server that appears to manage session import and memory operations; it likely needs companion tools for querying, managing, or configuring imports.
The surface only covers scanning and import status; obvious gaps include actually importing sessions, listing projects, or managing memory, leaving agents with no follow-up actions after a scan.