Enables real-time WebSocket monitoring of all MCP interactions for enhanced debugging and observation.
Most developer tooling work still happens through a UI a human drives. Proxy Sidecar MCP server moves it into the conversation instead. Enables real-time WebSocket monitoring of all MCP interactions for enhanced debugging and observation.
A <--MCP requests/responses--> B B <--IDE commands/responses--> C B --WebSocket notifications port 27042--> D
The server publishes 4 tools. What each one is for:
Requirements — The Requirements tool exposed by this serverBuild — 1. Install dependencies: bash pnpm install --frozen-lockfile 2. Build the project: bash pnpm buildContributing — 1. Fork the repository 2. Create your feature branch (git checkout -b feature/amazing-feature) 3. Commit your changes (git commit -m 'Add somePublishing — This package is published to npm with: - Provenance enabled for supply chain security - Automated releases via GitHub Actions when creating a newSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Configuration is passed through the environment: WS_PORT, IDE_PORT, HOST, LOG_ENABLED. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Proxy Sidecar's toolset — Requirements, Build, Contributing and 1 more — is a fair guide to whether it matches your workflow. It is maintained by dortegau; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Requirements | The Requirements tool exposed by this server. |
| Build | 1. Install dependencies: bash pnpm install --frozen-lockfile 2. Build the project: bash pnpm build |
| Contributing | 1. Fork the repository 2. Create your feature branch (git checkout -b feature/amazing-feature) 3. Commit your changes (git commit -m 'Add some amazing feature') 4. Push to the branch (git push origin feature/amazing-feat |
| Publishing | This package is published to npm with: - Provenance enabled for supply chain security - Automated releases via GitHub Actions when creating a new release - Public access on npm registry |
| Variable | Description | Required |
|---|---|---|
| WS_PORT | Configuration value read at startup. | Optional |
| IDE_PORT | Configuration value read at startup. | Optional |
| HOST | Endpoint or connection string the server talks to. | Optional |
| LOG_ENABLED | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.