SyncroNow AI MCP server
2026년 11월 3일 커밋AI 클라이언트가 ServiceNow scoped-app 코드를 일반 파일로 관리하고, Git 버전 관리 및 메타데이터와 종속성 분석을 수행할 수 있도록 지원합니다.
다른 이름 IvanBBaev/syncrona
- 스타
- 3
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 3일
- 라이선스
- GPL-3.0
SyncroNow AI MCP란?
AI 클라이언트가 ServiceNow scoped-app 코드를 일반 파일로 관리하고, Git 버전 관리 및 메타데이터와 종속성 분석을 수행할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
SyncroNow AI MCP server 정보
syncrona는 개발자가 현대적인 개발 워크플로우를 통해 ServiceNow scoped-app 코드를 관리할 수 있게 해줍니다. Scoped-app 코드를 편집 가능한 일반 파일 형태로 로컬 프로젝트 폴더에 다운로드함으로써 Git을 이용한 버전 관리가 가능하며, 이를 통해 실제 diff, 히스토리, 브랜치 및 pull request를 사용할 수 있습니다. 이는 ServiceNow 인스턴스 내부에만 존재하던 코드를 표준 저장소 형식으로 변환합니다.
사용자는 빌드 파이프라인을 통해 TypeScript, Babel, Webpack과 같은 현대적인 JavaScript 도구를 개발 프로세스에 통합할 수 있습니다. 이 MCP server는 Basic, OAuth (password, client credentials, JWT bearer), API key, Bearer token을 포함한 다양한 인증 방식을 지원합니다. Node.js 버전 22.0 이상이 필요하며, Windows 사용자는 WSL을 반드시 사용해야 합니다. 시스템은 AI 클라이언트에서 이러한 작업을 직접 수행할 수 있도록 63개의 MCP tool 세트를 제공합니다.
활용 사례
- 1ServiceNow 코드 버전 관리ServiceNow 소스 코드를 Git에서 관리하여 브랜치와 pull request 기능을 활용합니다.
- 2JavaScript 개발 현대화TypeScript 또는 Webpack을 사용하여 ServiceNow 코드를 빌드 파이프라인에서 실행합니다.
- 3Scoped application을 파일로 관리Scoped-app 코드를 편집 가능한 일반 파일로 변환하여 조작을 용이하게 합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
구성
SN_INSTANCE_DEVSN_PASSWORD_DEVSN_USER_DEV
| 이름 | 설명 | 유형 |
|---|---|---|
| SN_INSTANCE_DEV | — | |
| SN_PASSWORD_DEV | — | |
| SN_USER_DEV | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능ivanbbaev/syncrona is public and reachablegithub.com/ivanbbaev/syncrona ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)GPL-3.0spdx.org/licenses/GPL-3.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-03github.com/ivanbbaev/syncrona ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기SyncroNow AI
Built and maintained in my own time. If SyncroNow AI helps you or your team, a sponsorship keeps it moving — it directly funds new features, fixes and keeping pace with ServiceNow's REST surface.
Overview
SyncroNow AI is a tool for managing ServiceNow code in a more modern way. It allows you to:
- Store scoped app code in GitHub in an editable way.🐙 (Looking at you studio source control👀)
- Run your code through build pipelines that enable you to write modern JavaScript and use modern development tools such as TypeScript, Babel, and Webpack. 🎉
- Take control of your development process in ServiceNow! 💪
Because your scoped-app code is downloaded as plain, editable files in a project folder, SyncroNow AI is well suited for tracking your ServiceNow source code in Git — giving you real diffs, history, branches and pull requests over code that would otherwise live only inside the instance.
Coming from now-sdk? The ServiceNow SDK's everyday commands have a
syncronacounterpart:query,cicd,push --create/--prune,init --new, and the whole Fluent (.now.ts) toolchain throughsyncrona fluent(which drives@servicenow/sdkwhen you install it). See docs/MIGRATING_FROM_NOW_SDK.md for the command and environment-variable mapping and the honest list of what is not covered yet.push --create/--prune,init --new, the data-model sidecars,cicd run-suite/run-test,fluent installandquerywere verified against a live instance on 2026-10-13. Still covered only by mocked tests:cicd install/publish/rollback,fluent move-to-app, thesync_fluent_buildMCP tool and the composite data-model layout. Try those on a development instance first.
Project documentation
- docs/ARCHITECTURE.md — package graph, the two ServiceNow clients and their shared transport policy, push/manifest flows, MCP request pipeline, and the module contract for adding/removing CLI commands and MCP tool families (mermaid diagrams).
- docs/PRODUCT_STATE.md — what works today, phase history, known gaps and operating constraints.
- docs/MULTI_INSTANCE.md — credential precedence, instance profiles, the dev→prod workflow, and CI.
- docs/MONOREPO_GUIDE.md — multi-scope layout, per-scope vs shared config, and CI matrices.
- docs/PLUGIN_DEVELOPMENT.md — the plugin contract and how to write and wire your own build plugin.
- docs/BUSINESS_ANALYSIS.md — product vision, personas, value proposition, competitive positioning, KPIs, prioritized roadmap and risk register.
- docs/COMPARISON.md — SyncroNow AI vs ServiceNow native Git,
the ServiceNow SDK (
now-sdk/ Fluent), and update sets (one-page comparison). - docs/MIGRATING_FROM_NOW_SDK.md — coming
from the ServiceNow SDK (
now-sdk/ Fluent): command and environment-variable mapping, authentication differences, and what is not covered yet. - docs/ENTERPRISE_READINESS.md — what remains for a public 1.0 / enterprise release (done / scheduled / owner-gated).
- ROADMAP.md — shipped capabilities, what 1.0 closed, and what is still open past it (with owner-gated items called out).
- SECURITY.md — vulnerability reporting and data-handling.
- SUPPORT.md — getting help, diagnostics, support scope.
- docs/TROUBLESHOOTING.md — symptom → cause → fix index for auth, connectivity, proxy/TLS, manifest, watch-mode and MCP issues.
- CONTRIBUTING.md — dev setup, quality gates, conventions.
- CODE_OF_CONDUCT.md — community standards.
- packages/mcp-server/README.md — MCP server setup, tools, guardrails, and safety notes.
- docs/MCP_TOOLS.md — autogenerated API reference for all
63 MCP tools (parameters, safety flags; regenerated via
generate-tool-reference.js, drift-gated by its--checkmode). - packages/credential-store/README.md — the global encrypted credential store (AES-256-GCM at rest, key derivation) shared by the CLI and MCP server.
- packages/redaction/README.md — the shared secret-detection and redaction primitive: which key names and value shapes count as credentials, why detection fails closed, and what the redaction marker encodes.
- docs/VERSIONING.md — semver policy, lockstep releases, the MCP tool-contract stability promise, and the Node.js support window.
- CHANGELOG.md — notable changes per release.
Table of Contents
Installation
syncrona and all fifteen @syncrona/* packages are published on npm with build
provenance, so no build step is needed to use the CLI.
Global CLI quick start
npm i -g syncrona
syncrona login
syncrona init
Or without installing anything: npx syncrona init.
Install from source
For contributing, or to run an unreleased commit:
git clone https://github.com/IvanBBaev/syncrona
cd syncrona
npm ci
npm run build
# expose the CLI as `syncrona` on your PATH:
npm link --workspace syncrona
syncrona login
syncrona init
Prefer not to link globally? Run the built CLI directly from the repo with
node packages/core/dist/index.js <command>.
Requirements
In order to use SyncroNow AI, you will need:
- Node.js version 22.0 or later
⚠️ Windows users: WSL (Windows Subsystem for Linux) is currently required — native Windows is not yet supported.
- Install WSL with an Ubuntu distribution (Windows version 1903+; earlier versions are untested/not working)
- Run all
syncronacommands from inside the WSL shell- (Optional) Windows Terminal is recommended for proper text rendering
Native Windows support (PowerShell install, Windows Credential Manager) is on the roadmap.
ServiceNow compatibility: SyncroNow AI talks only to standard ServiceNow REST/Table APIs and needs nothing installed on the instance, so it is broadly release-agnostic. It is actively used against recent ServiceNow releases; a formal supported-version matrix is being established — if you hit a release-specific issue, please open an issue with your instance version.
Authentication: SyncroNow AI supports every inbound REST authentication method
ServiceNow offers, in both clients (CLI axios and the MCP server's native
fetch). Select the method explicitly with SN_AUTH_METHOD, or let it be inferred
for backward compatibility. Every auth variable also accepts a per-profile
_<PROFILE> suffix.
Method (SN_AUTH_METHOD) |
Required vars | Notes |
|---|---|---|
Basic — basic (default) |
SN_USER, SN_PASSWORD |
HTTP Basic over HTTPS. |
OAuth password — oauth-password |
SN_OAUTH_CLIENT_ID, SN_OAUTH_CLIENT_SECRET, SN_USER, SN_PASSWORD |
OAuth 2.0 Resource Owner Password grant; Bearer token from oauth_token.do, refreshed on expiry/401. |
OAuth client credentials — oauth-client-credentials |
SN_OAUTH_CLIENT_ID, SN_OAUTH_CLIENT_SECRET |
OAuth 2.0 Client Credentials grant — service-to-service, no user password (Tokyo+). |
OAuth JWT bearer — oauth-jwt-bearer |
SN_OAUTH_CLIENT_ID, SN_OAUTH_CLIENT_SECRET, SN_JWT_KEY |
OAuth 2.0 JWT Bearer grant. SN_JWT_KEY is a path to (or inline) RS256 private-key PEM; a fresh signed assertion is minted per token. Optional SN_JWT_KID / SN_JWT_ISS / SN_JWT_SUB / SN_JWT_AUD override the JWT header/claims (defaults derived from client id + user + instance). |
API key — api-key |
SN_API_KEY |
Inbound REST API Key sent as a header — default x-sn-apikey, override with SN_API_KEY_HEADER (Vancouver+). |
Bearer token — bearer |
SN_BEARER_TOKEN |
A pre-issued OAuth access token sent as Authorization: Bearer <token> (the counterpart of now-sdk's SN_SDK_SESSION_BEARER_TOKEN). Environment-only: never stored by syncrona login and never refreshed. When present it is inferred ahead of every other method. |
Without SN_AUTH_METHOD the method is inferred exactly as before — bearer when
SN_BEARER_TOKEN is set, then OAuth password when a client id/secret pair and
a password are present, otherwise Basic — so
existing setups keep working unchanged. An unrecognized value is an error
rather than a fallback: syncrona doctor reports Unknown SN_AUTH_METHOD "<value>"
and the MCP server refuses to start, so a typo can no longer resolve silently to a
different method. Use a dedicated least-privilege integration user.
An injected UI session (Fluent tier only). SN_SESSION_COOKIE (the session's
Cookie header) and SN_SESSION_TOKEN (its X-UserToken CSRF token) are the
counterparts of now-sdk's SN_SDK_SESSION_COOKIE / SN_SDK_SESSION_TOKEN. When
SN_SESSION_COOKIE is set, the fluent actions hand that session to the SDK as is,
ahead of the profile's method and without a login; a token without a cookie is an
error. It is not an auth method: every other command ignores it, and so does
fluent types --native, which uses the profile. Environment-only and un-suffixed:
syncrona login never stores it, clears a stale one from .env, and syncrona
never renews it — once the session expires, the action fails with the instance's 401.
Mutual TLS (client certificate) is orthogonal to the method above and combines
with any of them (or works alone): point SN_CLIENT_CERT and SN_CLIENT_KEY at
PEM files (plus SN_CLIENT_KEY_PASSPHRASE if the key is encrypted). It is applied
at the TLS layer in both the CLI and the MCP server.
syncrona login walks you through any of these interactively (method picker), or
runs non-interactively with flags — for example
syncrona login --auth-method api-key --api-key XXXX or
syncrona login --auth-method oauth-client-credentials --client-id … --client-secret ….
Secrets are kept in the encrypted global credential store; the JWT key and TLS
cert/key are referenced by path, never copied into it. See
SECURITY.md and docs/MULTI_INSTANCE.md.
Corporate proxies & custom TLS (G9): the CLI honors the standard
HTTPS_PROXY / HTTP_PROXY / NO_PROXY environment variables automatically, so
it works behind a corporate proxy with no extra configuration. For a corporate
or self-signed certificate authority, point SYNCRONA_CA_BUNDLE at a PEM CA
bundle (or set Node's built-in NODE_EXTRA_CA_CERTS, which also covers the MCP
server's native-fetch client, which ignores SYNCRONA_CA_BUNDLE). As a last resort for a throwaway test instance,
SYNCRONA_TLS_REJECT_UNAUTHORIZED=0 disables certificate verification — insecure,
never use it against a real instance.
Request timeout: every ServiceNow request the CLI makes (data path and OAuth
token endpoint alike) is bounded at 120 seconds. Raise or lower it with
SN_REQUEST_TIMEOUT in milliseconds — a large bulk download over a slow link may
need more, and 0 restores the old unbounded behaviour. An unparseable or
negative value falls back to the 120-second default rather than disabling the
timeout.
Request rate: each client (the CLI and the MCP server alike) sends at most 20
requests per second to an instance. Set SN_MAX_RPS to a whole number from 1 to
20 to go slower — on a shared or fragile instance, say. It can only lower the
cap: a value outside that range, or one that is not a whole number, stops the
command with an error rather than silently running at full rate. The MCP server
reads it from its own environment (the env block of the MCP client
configuration), not from the project .env.
Instructions
- Create a folder to store the scoped app code.
- In a terminal, run
npm initinside the newly created folder and follow the instructions to set up your node module. - Install
syncrona(nothing needs to be installed on the instance — the CLI works against the standard ServiceNow REST/Table APIs)
npm i -D syncrona
- Initialize your SyncroNow AI project
npx syncrona init
If your repository is a monorepo with many scoped apps under packages/, run SyncroNow AI from the specific scope directory, for example packages/cs. Each scope package should get its own .env, sync.config.js, and sync.manifest.json.
- Configure your project!
- OPTIONAL BUT HIGHLY RECOMMENDED Once your project is configured the way you like, you can commit and push it to a git repository for superior tracking and version control! Make sure to create a
.gitignorefile and ignorenode_modulesand.envbecause you really don't want those files in your repository. - Start dev mode and start working! Every time you save a file that is tracked by SyncroNow AI, it will be built with your ruleset and the result will be placed in ServiceNow!
npx syncrona dev
How does it work?
SyncroNow AI takes a two-pronged approach to managing your ServiceNow scoped app. Architecture, creation of records, deletion of records, metadata and other ServiceNow objects besides your actual source code will be managed normally. Your source code itself will be managed inside of your SyncroNow AI project.
SyncroNow AI MCP 질문
ServiceNow 인스턴스에 별도로 설치해야 하는 것이 있나요?
아니요, 표준 ServiceNow REST/Table API와 통신하므로 인스턴스에 별도의 로컬 설치가 필요하지 않습니다.
Windows 환경을 지원하나요?
아직 Windows 네이티브 환경은 지원하지 않습니다. Windows 사용자는 WSL(Windows Subsystem for Linux)을 사용해야 합니다.