SPOC

Name: SPOC
Author: SPOC-App

by SPOC-Appversion 0.1.3i★ –iRuns on your computer

Registry nameio.github.SPOC-App/mcp-bridge

Install

Overview

Description from the maker (original English)

stdio bridge for the SPOC MCP server — for Claude Desktop, Cursor, Zed

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: SPOC_BEARER

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SPOC_BEARER, SPOC_ENDPOINT, SPOC_EVENTS_ENDPOINT, SPOC_TIMEOUT_MS, SPOC_DISABLE_SSE, SPOC_DEBUG

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@spocapp/mcp-bridge"
      ],
      "env": {
        "SPOC_BEARER": "your-value",
        "SPOC_ENDPOINT": "your-value",
        "SPOC_EVENTS_ENDPOINT": "your-value",
        "SPOC_TIMEOUT_MS": "your-value",
        "SPOC_DISABLE_SSE": "your-value",
        "SPOC_DEBUG": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add bridge --env SPOC_BEARER=your-value --env SPOC_ENDPOINT=your-value --env SPOC_EVENTS_ENDPOINT=your-value --env SPOC_TIMEOUT_MS=your-value --env SPOC_DISABLE_SSE=your-value --env SPOC_DEBUG=your-value -- npx -y @spocapp/mcp-bridge

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@spocapp/mcp-bridge"
      ],
      "env": {
        "SPOC_BEARER": "your-value",
        "SPOC_ENDPOINT": "your-value",
        "SPOC_EVENTS_ENDPOINT": "your-value",
        "SPOC_TIMEOUT_MS": "your-value",
        "SPOC_DISABLE_SSE": "your-value",
        "SPOC_DEBUG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "bridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@spocapp/mcp-bridge"
      ],
      "env": {
        "SPOC_BEARER": "your-value",
        "SPOC_ENDPOINT": "your-value",
        "SPOC_EVENTS_ENDPOINT": "your-value",
        "SPOC_TIMEOUT_MS": "your-value",
        "SPOC_DISABLE_SSE": "your-value",
        "SPOC_DEBUG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SPOC_BEARER secret env
Bearer token from https://spoc.com/settings/api-keys. Omit for anonymous access; required for tools that need a principal (e.g. spoc.harness.issue).
SPOC_ENDPOINT env
HTTP JSON-RPC endpoint. Defaults to https://spoc.com/mcp/rpc.
SPOC_EVENTS_ENDPOINT env
SSE endpoint for server-initiated notifications. Defaults to https://spoc.com/mcp/events.
SPOC_TIMEOUT_MS env
HTTP request timeout in milliseconds. Defaults to 30000.
SPOC_DISABLE_SSE env
Set to 1 to skip the SSE event stream (notifications become unavailable).
SPOC_DEBUG env
Set to 1 to log debug output to stderr.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SPOC-App, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32700 servers in this category
Published to the registry more recently than 45% of the other 32700 servers in this category
Basic checks equal to or better than 100% of the other 32700 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SPOC safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SPOC_BEARER

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Agent Data Tools: Utilities

by Nutshell2000

103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@spocapp/mcp-bridge

Small stdio bridge that lets Claude Desktop, Cursor, Zed, Windsurf and other stdio-only MCP clients talk to the SPOC MCP server at spoc.com/mcp/rpc.

npm: @spocapp/mcp-bridge
MCP Registry: io.github.SPOC-App/mcp-bridge
Live server: https://spoc.com/mcp/rpc — reports itself as spoc / 1.27.0

What this is (and isn't)

Most current MCP clients only speak the stdio transport — JSON-RPC over a subprocess's stdin/stdout. SPOC's MCP server speaks HTTP+SSE so it can serve many clients at once. This bridge is the shim between the two: install it, point your MCP client at it, and SPOC's tools appear in the client's tool picker.

It is not a rewrite of the MCP protocol, and it doesn't cache, batch, or reinterpret requests. Every JSON-RPC frame goes through unchanged. If you need behaviour that differs from what the bridge does today, it's usually easier to fix in SPOC itself than in the shim.

Install

You don't need to install it — most MCP clients will fetch it on demand with npx:

npx -y @spocapp/mcp-bridge

Or install it once and point clients at the binary:

npm install -g @spocapp/mcp-bridge

which spoc-mcp-bridge

Configure your MCP client

Claude Desktop

Edit the config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

"mcpServers": { "spoc": { "command": "npx", "args": ["-y", "@spocapp/mcp-bridge"], "env": { "SPOC_BEARER": "spk_live_..." } } } }

Restart Claude Desktop. SPOC's tools should appear in the tool picker within a few seconds.

Cursor

~/.cursor/mcp.json (or Settings → MCP → Edit mcp.json):

"mcpServers": { "spoc": { "command": "npx", "args": ["-y", "@spocapp/mcp-bridge"], "env": { "SPOC_BEARER": "spk_live_..." } } } }

Zed

~/.config/zed/settings.json:

"context_servers": { "spoc": { "command": { "path": "npx", "args": ["-y", "@spocapp/mcp-bridge"], "env": { "SPOC_BEARER": "spk_live_..." } } } } }

Windsurf, Continue, etc.

Any client that speaks the MCP stdio transport works the same way. Set the command to npx -y @spocapp/mcp-bridge and pass a bearer via environment.

Environment variables

Variable	Default	Notes
`SPOC_BEARER`	_(unset)_	Token sent as `Authorization: Bearer …`. Omit for anonymous access. Required for tools that need a principal (e.g. `spoc.harness.issue`).
`SPOC_ENDPOINT`	`https://spoc.com/mcp/rpc`	HTTP JSON-RPC endpoint.
`SPOC_EVENTS_ENDPOINT`	`https://spoc.com/mcp/events`	SSE endpoint for server-initiated notifications.
`SPOC_TIMEOUT_MS`	`30000`	HTTP request timeout in milliseconds.
`SPOC_DISABLE_SSE`	_(unset)_	Set to `1` to skip the SSE event stream. Notifications become unavailable; everything else still works.
`SPOC_DEBUG`	_(unset)_	Set to `1` to log to stderr. Useful when your MCP client swallows errors silently.

Bearer tokens

Generate one at https://spoc.com/settings/api-keys. Make sure the `harness:issue` scope is checked or SPOC will reject calls that need to issue harnesses.

Anonymous access works for read-only tools that don't need a principal. Bearer is only required for tools that act on behalf of an identity.

Smoke test

Confirm the bridge and the upstream are both healthy:

npx -y @spocapp/mcp-bridge <<< '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}'

You should get a single JSON line back that includes "name":"spoc" and "version":"1.27.0". If you see that, MCP-aware clients will work.

Troubleshooting

Tools don't appear in the client after restart. Run the smoke test above in a plain terminal. If it returns an error frame, the error.data field will tell you why. If it returns nothing at all, check the client's log for a spawn error — the usual cause is npx not being on the client's PATH.

`ERR_INTERNAL` on tool calls. Almost always an upstream issue rather than a bridge issue. Set SPOC_DEBUG=1 and re-run — the bridge will log the raw upstream response.

401 errors. The bearer token is missing, wrong, or lacks scope. Verify at https://spoc.com/settings/api-keys.

SSE won't connect. Notifications are optional. Set SPOC_DISABLE_SSE=1 and everything except server-initiated notifications continues to work.

Testing

npm ci

npm run build npm test # unit + client-integration suites (offline, no network)

The client-integration suite spawns spoc-mcp-bridge as a real subprocess and drives it through the same stdio protocol that Claude Desktop, Cursor, Zed, and Windsurf use — initialize, notifications/initialized, tools/list, tools/call, concurrent in-flight calls, mixed-type ids, SSE notifications, upstream errors, and timeouts. If it passes, MCP clients that speak stdio will work.

To also exercise the real production endpoint:

SPOC_LIVE_TEST=1 npm test                              # anonymous only

SPOC_LIVE_TEST=1 SPOC_BEARER=spk_live_... npm test # + tools/call

CI runs the offline suite on Node 18 / 20 / 22 for every push and PR; the live suite runs on main only.

Writing your own client

If you're implementing SPOC's report-event HMAC signing directly (rather than going through this bridge), one thing to watch out for: SPOC's canonical form matches JavaScript JSON.stringify behaviour, which leaves non-ASCII characters as themselves rather than escaping them to \uXXXX. Python's default json.dumps(...) escapes non-ASCII — you'll get a bad_signature 401 the first time you include an em-dash, curly quote, or accented character. Pass ensure_ascii=False.

License

MIT

SPOC

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Agent Data Tools: Utilities

README from the maker

@spocapp/mcp-bridge

What this is (and isn't)

Install

Configure your MCP client

Claude Desktop

Cursor

Zed

Windsurf, Continue, etc.

Environment variables

Bearer tokens

Smoke test

Troubleshooting

Testing

Writing your own client

Links

License