Skip to main content
Glama
lokiwilded

suplagentics-mcp-server

by lokiwilded
README.md
# suplagentics-mcp-server

A standalone [Model Context Protocol](https://modelcontextprotocol.io) server exposing
SuplAgentics's real capabilities — Import History today, more over time — to any MCP-capable
client (opencode, Claude Code, Claude Desktop), not just one dashboard.

## What this is

SuplAgentics is a set of tools built on top of [opencode](https://opencode.ai) and
[opencode-mem](https://github.com/anthropics/opencode-mem) for importing existing Claude Code /
opencode session history into a searchable memory store, and surfacing improvement suggestions
mined from that history. This package is the portable capability layer — the same logic used by
the [SuplAgentics dashboard](https://www.npmjs.com/package/suplagentics) (an OpenChamber-based
web UI), but callable directly by any MCP client.

## Install

```bash
npm install -g suplagentics-mcp-server
```

## Register with opencode

Add to `~/.config/opencode/opencode.json` (or your project's own config for project-only scope):

```json
{
  "mcp": {
    "suplagentics": {
      "type": "local",
      "command": ["node", "/path/to/suplagentics-mcp-server/src/index.js"],
      "enabled": true
    }
  }
}
```

A `user`-scope entry (the example above) applies to every project automatically — no per-project
setup needed.

## Tools

- `suplagentics_import_scan` — scans this machine for opencode session history (`opencode.db`)
  and Claude Code session history (`~/.claude/projects/`) not yet imported into opencode-mem.
  Returns real per-project session/memory counts and import status.

More tools are on the way as more of the underlying capability gets exposed directly.

## License

MIT

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of overlap or confusion; its purpose is singular and clearly stated.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues