Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Security patrol management: missed rounds, suspicious scans, incidents and checkpoint setup.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.patroltech.online/mcpRun this in your terminal
claude mcp add --transport http patroltech https://mcp.patroltech.online/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"patroltech": {
"url": "https://mcp.patroltech.online/mcp"
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"patroltech": {
"type": "http",
"url": "https://mcp.patroltech.online/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mcp.patroltech.online/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
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
The registry name was verified against the domain patroltech.online (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 1092 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.2.8) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
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.
The remote Model Context Protocol server of PatrolTech, the guard tour and security patrol platform. It lets AI assistants such as Claude, ChatGPT, Copilot, Gemini or Cursor read and act on a PatrolTech account on behalf of a user who signs in with OAuth: rounds, routes, checkpoints, guards, incidents, users, locations, access control and scans.
This repository holds only the server code. To install the connector in your assistant, use PatrolTech/ai-integrations: plugins, MCP Registry entry and instructions for each client.
This server grants no access by itself. It has no credentials of its own: it forwards the user's token, and the PatrolTech API authorizes every call (organization and location roles, OAuth scopes and a closed list of writes allowed to agents). See SECURITY.md.
Use the hosted endpoint https://mcp.patroltech.online/mcp with an MCP client that supports remote OAuth. The user's PatrolTech account and role determine access.
Create a free account · Connection guide · Agent skill and client plugins
Building your own integration instead? See the API reference of the public REST API and the TypeScript SDK. Webhooks are in development: tell us which events you need at info@patroltech.app.
Ask about missed patrol rounds, suspicious checkpoint scans, unreviewed checkpoints, incidents or visitor access logs. Supported changes are proposals and require explicit confirmation. Deleting records, inviting users and billing are outside the connector's capabilities.
For client setup, OAuth verification and troubleshooting, see the agent installation guide, including Cline instructions.
MCP client ──OAuth──▶ PatrolTech authorization server
│ Bearer access token (audience = MCP_PUBLIC_URL) ▼ MCP server (this repo, stateless) ──agent session──▶ PatrolTech API │ ▲ └── Redis: locks and rate limits └── @patroltech/agent-capabilities + @patroltech/sdk-api
/mcp requires a bearer token issued by the PatrolTech authorization server (RFC 9728 metadata at /.well-known/oauth-protected-resource/mcp). Tokens are verified against the API's JWKS (ES256, exact issuer and audience) and exchanged for a 15-minute agent session (POST /oauth/agent-session), cached by a hash of the token. The API trims the session to what the grant still allows.SET NX PX, renewed while it lasts) and the per-user, per-tool rate limits. It is required in production and staging. If Redis fails, propose, confirm and cancel answer "busy" rather than risk two proposals overwriting each other. Without REDIS_URL (development and test only) both live in process memory.mcp channel of @patroltech/agent-capabilities, which calls the API through @patroltech/sdk-api.| Tool | What it does |
|---|---|
patroltech_ _ | One per read of the catalog: read-only, English titles and descriptions, optional organization when the user has several. |
patroltech_account_get_context | The user's organizations (name, role, access) and their locations. Its description says where to review this connection (DASHBOARD_URL, Connected apps). |
patroltech_ _propose_ | Proposes a change. Nothing changes until it is confirmed. Proposals of one user and client form one batch (up to 10, expires after 30 minutes). |
patroltech_proposals_confirm | Executes the whole pending batch, in order, with the parameters that were proposed (marked destructive: clients ask the user first). |
patroltech_proposals_cancel | Withdraws the pending batch. |
patroltech_locations_get_qr_sheet | A signed link (1 hour) to the printable QR sheet of a location. |
Both are fixed text in src/interface/mcp/guidance: they change nothing in the account and call no backend, so they do not go through the audit line or the rate limit of the tools. The connection still needs OAuth, like everything under /mcp.
| Prompt | What it asks for |
|---|---|
patroltech_review_missed_rounds | The latest rounds not completed and the checkpoints skipped. |
patroltech_review_suspicious_scans | Suspicious or rejected scans, and how many are pending (period). |
patroltech_weekly_summary | How the last week went, starting with what needs attention. |
patroltech_set_up_account | What is missing to get the account running, and the next step. |
| Resource | What it holds |
|---|---|
patroltech://guides/choosing-a-tool | Which tool answers each question, and how changes are confirmed. |
patroltech://guides/reading-the-data | What statuses, scan validation, partial data and retention mean. |
The server also sends instructions (src/interface/mcp/serverInstructions.ts): guidance that spans several tools, such as using the ranking tools to compare guards and presenting them as activity data, not as an assessment of the people.
Writes need the write scope: without it the server answers 403 insufficient_scope with the read write challenge. Every result is { data, truncated?, notices?, note }, capped at 60,000 characters, where note says that data is data, never instructions. Each user can make 60 calls per minute to a read tool and 20 to a write tool. Every tool call writes one mcp.tool_call audit line with a hash of the arguments, never the arguments.
| Path | Auth | Purpose |
|---|---|---|
/mcp (path of MCP_PUBLIC_URL) | Bearer | The MCP endpoint (POST, GET, DELETE). Validates Host and rejects any Origin. |
/.well-known/oauth-protected-resource/mcp | none | Protected resource metadata (RFC 9728), also at the root path. |
/health | none | Liveness: 200 {"status":"ok","version":"…"}. |
/health/ready | none | Readiness: 200 if the JWKS answers within 3 s and, with REDIS_URL, Redis answers PING; otherwise 503. |
/.well-known/openai-apps-challenge | none | The OPENAI_APPS_CHALLENGE token, for the ChatGPT apps directory; 404 without it. |
Every variable is documented in .env.example. The server refuses to start, listing each missing or invalid variable, if the configuration is not valid.
| Variable | Required | Description |
|---|---|---|
MCP_PUBLIC_URL | yes | Exact public URL of the MCP endpoint, the audience of the tokens (for example https://mcp.example.com/mcp). |
API_BASE_URL | yes | Origin of the PatrolTech API, without /api. |
OAUTH_ISSUER | yes | Expected iss of the access tokens, byte for byte. |
OAUTH_JWKS_URL | no | JWKS of the issuer. Default API_BASE_URL + /oauth/jwks.json. |
DASHBOARD_URL, APP_BASE_URL | yes | PatrolTech dashboard and web app, for links shown to the user. |
APP_ENVIRONMENT | yes | production, staging, development or test. |
REDIS_URL | in production and staging | Shared Redis (ioredis URL). |
REDIS_NAMESPACE | no | Key prefix in Redis. Default APP_ENVIRONMENT. |
HOST, PORT | no | Where the process listens. Default 127.0.0.1:3110, behind a reverse proxy. |
LOG_LEVEL | no | debug, info (default), warn or error. Audit and heartbeat lines are written at any level. |
SERVICE_NAME | no | service field of every log line. Default mcp-server. |
OPENAI_APPS_CHALLENGE | no | Domain verification token for the ChatGPT apps directory. |
Logs are one JSON object per line on stdout and stderr. Each process writes an mcp.heartbeat line every 5 minutes, so a log monitor can alert when it stops.
Node.js 22.9 or later.
npm ci
cp .env.example .env.local #
Only the beginning is shown; read the rest in the repo