
ArcSync
io.github.VanLandinghamLabsPublished by GitHub account VanLandinghamLabsv0.3.9Updated Nov 7, 2026
Architecture graphs from Terraform, CDK, CloudFormation, Pulumi and ARM, for coding agents
Overview
ArcSync MCP gives coding agents the architecture graph parsed from your infrastructure-as-code, plus tools to validate and push diagrams.
- What you can do
- List and read architecture diagrams as Mermaid or JSON, with a canvas link
- Describe individual resources and compare versions or deltas
- Start and track parsing of infrastructure-as-code sources
- Validate diagrams locally, push them to get canvas and Notion embed links, and fetch diagram source
- List available icons for diagram authoring
- When to use it
- Useful when a coding agent needs to reason about existing cloud infrastructure defined in Terraform, CDK, CloudFormation, Pulumi, ARM or Serverless, or when you want an agent to draft, check and publish architecture diagrams.
- Requirements
- Runs locally over stdio via npx (Node.js) or a standalone binary installed with Homebrew or from Releases. An ArcSync account is needed: connect through the browser on first use, or supply ARCSYNC_CLIENT_ID and ARCSYNC_CLIENT_SECRET for CI or shared machines. Desktop only.
Installation
In SourceWeft
- Open ArcSync in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
arcsync-mcp
An MCP server that gives coding agents (Claude Code, Cursor, GitHub Copilot and other MCP clients) the architecture graph ArcSync parsed from your infrastructure-as-code: Terraform, AWS CDK, CloudFormation, Pulumi, Azure ARM and Serverless Framework.
Tools: list_diagrams, get_diagram (Mermaid or JSON, plus a canvas link), describe_resource, get_delta, list_versions, start_parse, get_parse_status. For diagrams the agent writes itself: validate_diagram (local check), push_diagram (store it and get canvas and Notion embed links), get_diagram_source, list_icons.
Setup
Add to .mcp.json (no credential in it, so it is safe to commit):
Claude Desktop
Download arcsync-mcp-<version>.mcpb from the latest release and open it: Claude Desktop installs the extension, with no config file to edit. Leave the two credential fields empty to connect in the browser (below), or fill in both with an MCP credential from Settings.
Without Node.js
Each release also ships a standalone binary. On macOS or Linux, Homebrew installs it (on Intel Macs, Homebrew installs the npm package on its own Node.js instead):
On Windows, or without Homebrew, download the archive for your platform from Releases and check it with gh attestation verify <archive> -R VanLandinghamLabs/arcsync-mcp. Then use "command": "arcsync-mcp" with no args, and arcsync-mcp login / logout in place of the npx forms below.
The server is listed in the MCP Registry as io.github.VanLandinghamLabs/arcsync-mcp.
Connect
The first tool call that reaches ArcSync returns a link to https://arcsync.dev/settings/mcp/connect. validate_diagram and list_icons work without connecting. Open it, sign in, and click Connect: ArcSync mints an MCP credential and hands it to the server over 127.0.0.1, which saves it to ~/.config/arcsync/mcp-credential.json (mode 0600) and uses it from the next call. From a terminal, npx -y arcsync-mcp login does the same; npx -y arcsync-mcp logout deletes the saved file.
For CI or a shared machine, create an MCP credential at https://arcsync.dev/settings instead and pass ARCSYNC_CLIENT_ID and ARCSYNC_CLIENT_SECRET in the server's environment; they take precedence over a saved credential.
Two agent skills ship in skills/: arcsync-mcp tells an agent when to call each graph tool, and arcsync-diagrams teaches it to write, validate and push its own diagrams. Install both for Claude Code, Codex, Cursor and the other agents the skills CLI supports:
The skills do not install the server; add it as above.
Full guide: https://arcsync.dev/docs/mcp
Source and development
This repository is mirrored from the ArcSync monorepo on each release, together with the ArcSync core modules the server uses (vendor/core/). Releases are published to npm from here with provenance, so npm view arcsync-mcp --json links each version to the commit and workflow run that built it. Issues and pull requests are welcome; accepted changes are ported to the monorepo and ship in the next release.
License
MIT
Source: README.md at commit d2a7c99
Tools
0Version history
8- v0.3.9LatestNov 7, 2026
- v0.3.6Nov 6, 2026
- v0.3.5Nov 5, 2026
- v0.3.4Nov 5, 2026
- v0.3.3Nov 4, 2026
- v0.3.2Nov 4, 2026
- v0.3.1Nov 3, 2026
- v0.2.1Nov 1, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts