MCP Server JSON Sync

Created By
danielrosehilla year ago
Sync script for syncing VS Code MCP server JSON to Roo Code's store
Overview

What is MCP Server JSON Sync?

MCP Server JSON Sync is a synchronization script designed to keep Model Context Protocol (MCP) server configurations in sync between VS Code and various AI assistants, ensuring a single source of truth for configurations.

How to use MCP Server JSON Sync?

To use the MCP Server JSON Sync, navigate to the appropriate directory for your target AI assistant and run the installation script. This will set up a systemd timer to automatically sync configurations every hour.

Key features of MCP Server JSON Sync?

  • Synchronizes MCP server configurations from VS Code to multiple AI assistants.
  • Supports automated hourly syncing via systemd timers.
  • Provides a manual sync option for immediate updates.

Use cases of MCP Server JSON Sync?

  1. Keeping AI assistant configurations up-to-date with changes made in VS Code.
  2. Simplifying the management of multiple AI assistants by centralizing configuration in VS Code.
  3. Automating the synchronization process to reduce manual errors.

FAQ from MCP Server JSON Sync?

  • What AI assistants are supported?

Currently, it supports Cline, RooCode, and Windsurf.

  • How often does the sync occur?

The sync occurs automatically once per hour.

  • Can I manually sync configurations?

Yes, you can use the manual sync script to sync configurations immediately.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
danielrosehill
Star
0
Language
Shell
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago