Bridgistic runs on your own machine — the client starts it, so there is no endpoint to ping. 81 installs a week from npm. Last commit 7 Nov 2026.
Connect Claude to WordPress safely: signed requests, scoped keys, approvals, logs, snapshots.
We read the source, 18 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет bridgistic-mcp-server ссылается на shubochandrosarker/bridgistic-claude-marketplace
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add bridgistic -e 'BRIDGISTIC_SITE_URL=<BRIDGISTIC_SITE_URL>' -e 'BRIDGISTIC_KEY_ID=<BRIDGISTIC_KEY_ID>' -e 'BRIDGISTIC_KEY_SECRET=<BRIDGISTIC_KEY_SECRET>' -- npx -y bridgistic-mcp-server
{
"mcpServers": {
"bridgistic": {
"command": "npx",
"args": [
"-y",
"bridgistic-mcp-server"
],
"env": {
"BRIDGISTIC_KEY_ID": "<BRIDGISTIC_KEY_ID>",
"BRIDGISTIC_KEY_SECRET": "<BRIDGISTIC_KEY_SECRET>",
"BRIDGISTIC_SITE_URL": "<BRIDGISTIC_SITE_URL>"
}
}
}
}
[mcp_servers.bridgistic]
command = "npx"
args = ["-y", "bridgistic-mcp-server"]
env = { BRIDGISTIC_SITE_URL = "<BRIDGISTIC_SITE_URL>", BRIDGISTIC_KEY_ID = "<BRIDGISTIC_KEY_ID>", BRIDGISTIC_KEY_SECRET = "<BRIDGISTIC_KEY_SECRET>" }
{
"mcpServers": {
"bridgistic": {
"command": "npx",
"args": [
"-y",
"bridgistic-mcp-server"
],
"env": {
"BRIDGISTIC_KEY_ID": "<BRIDGISTIC_KEY_ID>",
"BRIDGISTIC_KEY_SECRET": "<BRIDGISTIC_KEY_SECRET>",
"BRIDGISTIC_SITE_URL": "<BRIDGISTIC_SITE_URL>"
}
}
}
}
{
"servers": {
"bridgistic": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bridgistic-mcp-server"
],
"env": {
"BRIDGISTIC_KEY_ID": "<BRIDGISTIC_KEY_ID>",
"BRIDGISTIC_KEY_SECRET": "<BRIDGISTIC_KEY_SECRET>",
"BRIDGISTIC_SITE_URL": "<BRIDGISTIC_SITE_URL>"
}
}
}
}
Put your own values in place of
<BRIDGISTIC_SITE_URL> (WordPress site URL exactly as shown in WP Admin → Settings → General, e.g. https://example.com), <BRIDGISTIC_KEY_ID> (Public key id (wpk_…) from WP Admin → Bridgistic → Claude Setup), <BRIDGISTIC_KEY_SECRET> (Key secret (wps_…) shown once at key creation).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BRIDGISTIC_CONNECTIONS (Optional absolute path to a multi-site connections JSON registry (alias → siteUrl/keyId/secret)), BRIDGISTIC_LOG_LEVEL (error | warn | info | debug (stderr only, never logs secrets)).
Connect Claude to WordPress safely: signed requests, scoped keys, approvals, logs, snapshots.
OAuth 2.1 short-link tools for AI agents with scoped tokens, approvals, audit logs, and revocation.
Free, no signup: per-app keys, allowed calls, approvals and an audit log for your API or model key.
Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.
Local LLM does Claude's bulk work: reads logs and files, researches the web, writes test-gated code.
Local LLM does Claude's bulk work: reads logs and files, researches the web, writes test-gated code.
Compress logs, retrieval chunks, and code context into structured LLM-ready signal.
Monitor cron jobs and recurring work through a project-scoped Watchgoose connection.
Answers built from our own checks of this server.