Big News: Socket raises $60M Series C at a $1B valuation to secure software supply chains for AI-driven development.Announcement
Sign In

@polygraph/mcp

Package Overview
Dependencies
Maintainers
4
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@polygraph/mcp

A Model Context Protocol server for coordinating cross-repository changes via Polygraph

latest
npmnpm
Version
0.1.29
Version published
Weekly downloads
558
Maintainers
4
Weekly downloads
 
Created
Source

Nx Logo

Polygraph MCP

A Model Context Protocol server for coordinating cross-repository changes via Polygraph.

npm version License
MCP Claude Code

Getting Started · Tools · Authentication · Learn More

Overview

Polygraph MCP enables AI coding agents to orchestrate synchronized changes across multiple repositories. It connects to Polygraph to manage sessions where a parent agent can delegate work to child agents in dependent repos, push branches, create linked pull requests, and monitor CI — all through a standard MCP interface.

Getting Started

Prerequisites

  • An account with Polygraph enabled
  • Authentication credentials (see Authentication)

Installation

Claude Code (with Polygraph plugin)

The recommended way to use Polygraph with Claude Code is via the Nx AI Agent Skills plugin, which includes Polygraph skills, subagents, and the MCP server pre-configured. Add this to your project's .claude/settings.json:

{
  "enabledPlugins": {
    "polygraph@nx-claude-plugins": true
  },
  "extraKnownMarketplaces": {
    "nx-claude-plugins": {
      "source": {
        "source": "github",
        "repo": "nrwl/nx-ai-agents-config"
      }
    }
  }
}

MCP server only

If you just need the MCP server without the full plugin, add it to your .mcp.json:

{
  "mcpServers": {
    "polygraph": {
      "command": "npx",
      "args": ["-y", "@polygraph/mcp@latest"]
    }
  }
}

Other AI agents

For Cursor, GitHub Copilot, Gemini, and other AI coding assistants, see Nx AI Agent Skills for Polygraph skills and configuration tailored to each platform.

Tools

Polygraph MCP exposes authentication and workflow tools for managing cross-repository changes:

Authentication

ToolDescription
whoamiShow current auth status and selected organization
loginAuthenticate with either a token or the default CLI login flow
logoutClear locally stored Polygraph credentials
list_accountsList organizations available to the current user
select_accountSelect the organization to operate on

Session Management

ToolDescription
list_reposDiscover available repos and their dependency relationships
start_sessionInitialize a new Polygraph session
show_sessionRetrieve session details, status, and linked PRs
list_sessionsList existing Polygraph sessions
add_repoAdd specific repository refs directly to a running session
link_referenceLink an external reference to a session
update_sessionUpdate the session title and/or description timeline
archive_sessionArchive a session

Agent Delegation

ToolDescription
spawn_agentDelegate tasks to child agents in other repositories
show_agentMonitor status and output of delegated tasks
stop_agentCancel an in-progress delegated task

Git & Pull Requests

ToolDescription
push_branchPush a local branch to its remote
create_prCreate draft PRs with session metadata linking
mark_pr_readyTransition PRs from draft to open
associate_prLink an existing PR to the session

CI Integration

ToolDescription
get_ci_logsRetrieve logs for GitHub Actions CI jobs

Resources

Polygraph MCP exposes repositories and recent sessions as MCP resources, which compatible clients (e.g. Claude Code) surface as @-mention completions.

URIContent
polygraph://repos/<repo-id>Repository metadata as JSON
polygraph://sessions/<session-id>Session details (status, description timeline, PRs) as JSON

Only sessions created within the last 30 days are registered (server-side filter via --since and --limit=100 on the underlying polygraph session list call).

Authentication

Polygraph MCP resolves credentials from the following sources (in priority order):

  • Environment variablesNX_CLOUD_AUTH_TOKEN or NX_CLOUD_ACCESS_TOKEN
  • nx-cloud.env — Project-level env file
  • nx.json — Project-level Nx configuration
  • ~/.nxcloud.ini — User-level configuration (or XDG config path)

login accepts an optional token. When a token is provided it uses headless login; otherwise it runs polygraph auth login --json and relies on the CLI's default auth flow.

Learn More

License

MIT

Keywords

nx

FAQs

Package last updated on 12 Jun 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts