mcpField
J
jsboige-mcp-servers

jsboige-mcp-servers

Local
github.com/jsboigeAI & Agents1Updated today
Repository

About jsboige-mcp-servers

jsboige-mcp-servers is a collection of MCP servers in the roo-extensions project, aimed at extending LLM workflows with project coordination and agent capabilities. Its active servers include roo-state-manager for cross-machine RooSync coordination and sk-agent for multi-agent conversations and vector memory.

Key features

  1. 0117 roo-state-manager MCP tools
  2. 02Cross-machine RooSync coordination
  3. 03Conversation browsing and summaries
  4. 04Semantic search using Qdrant and embeddings
  5. 05sk-agent multi-agent conversations
  6. 06Per-agent vector memory

Use cases

  1. 01Coordinating RooSync across machines
  2. 02Browsing and summarizing Roo and Claude Code conversations
  3. 03Searching indexed codebase and RooSync content
  4. 04Running multi-agent conversations with stored memory

MCP support

The repository contains active MCP servers. roo-state-manager exposes tools and resources for conversations, RooSync, dashboards, semantic search, and baselines; sk-agent provides an LLM proxy with MCP plugin tool calling.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

jsboige-mcp-servers

Collection de serveurs MCP (Model Context Protocol) pour étendre les capacités des modèles de langage (LLM).

CI License: MIT

CI

  • Workflow (.github/workflows/ci.yml): build + vitest for roo-state-manager
  • Branch protection: CI must pass before merge on main
  • Configs: vitest.config.ts (dev) / vitest.config.ci.ts (CI, excludes 12 declared test-file entries — census: servers/roo-state-manager/docs/CI-EXCLUSIONS-CENSUS.md)

Qu'est-ce que MCP?

Le Model Context Protocol (MCP) est un protocole qui permet aux modèles de langage (LLM) d'interagir avec des outils et des ressources externes.

Ce protocole permet d'étendre considérablement les capacités des LLM en leur donnant accès à:

  • Recherche d'informations en temps réel
  • Accès à des API externes
  • Manipulation de fichiers
  • Analyse de code
  • Coordination multi-agent (RooSync)
  • Et bien plus encore

Contenu du dépôt

Ce dépôt est un submodule du projet principal roo-extensions. Les serveurs MCP sont placés dans le répertoire servers/:

Serveurs actifs
roo-state-manager (Principal)

Le composant central du système RooSync Multi-Agent:

  • 17 outils MCP pour la coordination multi-machine
  • Conversations: browse, view, tree, summarize (Roo + Claude Code)
  • RooSync: send, read, manage, heartbeat, compare_config
  • Dashboards: global, machine, workspace (cross-machine coordination)
  • Indexation sémantique: Qdrant + embeddings (codebase_search, roosync_search)
  • Baselines: update, version, restore, export

Stack: TypeScript, Node.js 20.18.0, Vitest (~7900 tests) Doc: servers/roo-state-manager/README.md

sk-agent

Agent-centric LLM proxy server for Claude Code and Roo Code.

  • Multi-agent conversations (DeepSearch, DeepThink)
  • Vector memory per-agent via Qdrant
  • Tool calling via MCP plugins (SearXNG, Playwright)
  • Vision support (image, video, document analysis)

Stack: Python, Semantic Kernel, FastMCP Doc: servers/sk-agent/README.md

Serveurs retirés

Serveurs retirés du config actif (les 1er et 3e : code supprimé de servers/ en 09/2026, Epic #2639 tâche C) :

  • quickfiles-server — remplacé par les capacités natives de Claude Code (code supprimé 09/2026)
  • jinavigator-server — remplacé par markitdown MCP
  • github-projects-mcp — remplacé par gh CLI (code supprimé 09/2026)

Installation

Prérequis
  • Node.js 20.18.0 (version CI)
  • npm 10.x ou supérieur
  • Git
  • Python 3.10+ (pour sk-agent)
Installation rapide
# Cloner le dépôt (comme submodule)
git clone --recurse-submodules https://github.com/jsboige/roo-extensions.git
cd roo-extensions/mcps/internal

# Installer roo-state-manager
cd servers/roo-state-manager && npm install && npm run build
Installation individuelle
roo-state-manager
cd servers/roo-state-manager
npm install && npm run build
npx vitest run  # NEVER npm test (watch mode blocks)
sk-agent
cd servers/sk-agent
pip install -r requirements.txt
# See servers/sk-agent/README.md for configuration

Architecture

servers/
├── roo-state-manager/   # TypeScript — 17 tools, RooSync core
│   ├── src/tools/       # Tool definitions + handlers
│   ├── src/services/    # Business logic (RooSync, Qdrant, heartbeat)
│   ├── src/resources/   # MCP resources
│   └── tests/           # ~7900 vitest tests
├── sk-agent/            # Python — LLM proxy, multi-agent
│   ├── sk_agent.py      # FastMCP entry point
│   └── sk_conversations.py
└── (retired: quickfiles, jinavigator, github-projects)

Développement

Avant de committer
  1. Build: npm run build (serveurs TypeScript)
  2. Tests: npx vitest run (JAMAIS npm test — watch mode blocks)
  3. CI config: npx vitest run --config vitest.config.ci.ts (exclut 12 fichiers de tests déclarés — recensement : servers/roo-state-manager/docs/CI-EXCLUSIONS-CENSUS.md)

Contribution

Ce dépôt est un submodule de roo-extensions.

  1. Consulter les issues ouvertes
  2. PR obligatoire — pas de push direct sur main
  3. Configurer les variables d'environnement (voir .env.example)

Licence

MIT - voir LICENSE

Ressources

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.