SyncroNow AI MCP server
Commit 3 Nov 2026Memungkinkan AI client untuk mengelola kode scoped-app ServiceNow sebagai file biasa, melakukan versioning Git, serta menjalankan analisis metadata dan dependency.
Juga dikenal sebagai IvanBBaev/syncrona
- Stars
- 3
- Tools
- β
- Unduhan, 30 hari
- β
- Versi terbaru
- β
- Commit terakhir
- 3 Nov 2026
- Lisensi
- GPL-3.0
Apa itu SyncroNow AI MCP?
Memungkinkan AI client untuk mengelola kode scoped-app ServiceNow sebagai file biasa, melakukan versioning Git, serta menjalankan analisis metadata dan dependency.
Ringkasan dibuat dari README proyek
Tentang SyncroNow AI MCP server
syncrona memungkinkan developer untuk mengelola kode scoped-app ServiceNow melalui workflow pengembangan modern. Dengan mengunduh kode scoped-app sebagai file biasa yang dapat diedit ke dalam folder proyek lokal, Anda dapat menggunakan Git untuk version control, sehingga mendapatkan akses ke real diffs, history, branches, dan pull requests. Hal ini mengubah kode yang sebelumnya hanya ada di dalam instance ServiceNow menjadi format repository standar.
User dapat mengintegrasikan proses pengembangan mereka dengan tool JavaScript modern seperti TypeScript, Babel, dan Webpack melalui build pipelines. MCP server ini mendukung berbagai metode autentikasi termasuk Basic, OAuth (password, client credentials, dan JWT bearer), API keys, dan Bearer tokens. Sistem ini memerlukan Node.js versi 22.0 atau yang lebih baru dan mewajibkan penggunaan WSL bagi pengguna Windows. Sistem ini menyediakan 63 MCP tools untuk memfasilitasi operasi tersebut secara langsung dari AI client.
Apa yang bisa Anda lakukan dengannya
- 1Version control kode ServiceNowLacak source code ServiceNow Anda di Git untuk mendapatkan akses ke branches dan pull requests.
- 2Modernisasi pengembangan JavaScriptJalankan kode ServiceNow Anda melalui build pipelines menggunakan TypeScript atau Webpack.
- 3Kelola scoped applications sebagai fileKonversi kode scoped-app menjadi file biasa yang dapat diedit agar lebih mudah dimanipulasi.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Konfigurasi
SN_INSTANCE_DEVSN_PASSWORD_DEVSN_USER_DEV
| Nama | Deskripsi | Tipe |
|---|---|---|
| SN_INSTANCE_DEV | β | |
| SN_PASSWORD_DEV | β | |
| SN_USER_DEV | β |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap βBelum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks Β· Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauivanbbaev/syncrona is public and reachablegithub.com/ivanbbaev/syncrona βLolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)GPL-3.0spdx.org/licenses/GPL-3.0.html βLolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-03github.com/ivanbbaev/syncrona βLolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubSyncroNow 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.
Pertanyaan tentang SyncroNow AI MCP
Apakah perlu menginstal sesuatu di instance ServiceNow?
Tidak, tool ini hanya berkomunikasi dengan standard ServiceNow REST/Table API dan tidak memerlukan instalasi lokal di dalam instance tersebut.
Apakah Windows native didukung?
Windows native belum didukung; pengguna Windows wajib menggunakan WSL (Windows Subsystem for Linux).