graphistry

Drive a live Graphistry visualization session from any MCP client. Covers connecting to the viz MCP endpoint, personal-key and JWT auth, session ownership, the tool surface, and GFQL sent as JSON over the wire. Use when an external agent must query or recolor…

Umbrella router for Graphistry workflows across SDK and API surfaces. Use when asked to "use graphistry", "visualize with graphistry", "graph this data in graphistry", "graphistry plot", or any question mixing Python SDK and REST API concerns. Also triggers…

Construct and run GFQL graph queries in PyGraphistry using chain-list syntax or Cypher strings. Use when asked to "query my graph with GFQL", "MATCH pattern in graphistry", "find paths between nodes", "hop constraints", "let bindings", "GRAPH constructor", or…

Graphistry Hub REST API: auth, upload, URL controls, sessions, and sharing. Use when asked to "call the graphistry API with curl", "get a JWT token from graphistry", "upload a graph via REST", "graph.html URL parameters", "graphistry session API", or "share a…

PyGraphistry graph ML/AI: UMAP, DBSCAN, embeddings, and anomaly detection workflows. Use when asked to "run UMAP on my graph", "cluster nodes", "find anomalies in my network data", "embed nodes", "fit-transform pipeline", "semantic search over graph nodes",…

PyGraphistry connector workflows for external data sources and graph databases. Use when asked to "connect graphistry to Neo4j", "load from Splunk into graphistry", "query Kusto/ADX and visualize", "Databricks graph", "TigerGraph with pygraphistry", "ingest…

Core PyGraphistry workflow: auth, DataFrame-to-graph shaping, and first interactive plot. Use when asked to "register graphistry", "get started with pygraphistry", "plot my edges dataframe", "graphistry.register()", "bind src and dst columns", "make a…

TOC router for PyGraphistry Python SDK tasks. Use when asked to "plot a graph", "visualize my edges", "load a dataframe into graphistry", "import graphistry", "run UMAP on my graph", "query my graph with GFQL or Cypher", "pick an execution engine", "make my…

Editorial policy for user-facing documentation (docs/source/**). Use when writing or reviewing prose in docs pages, docstrings that render in docs, or release notes. Plain, direct, forward-readable text; no internal process talk; no AI-writing tells.

OPT-IN file-based planning for multi-session tasks. Only use when user explicitly requests it or work spans multiple sessions. For single-session work, prefer your platform's native planning features.

Structured PR review for pygraphistry. Input: PR number/branch (default current branch PR). Output: findings and convergence artifacts under the local task plans directory. Method: multi-wave, evidence-first review across spec, correctness, tests, security,…

Methodical bug-driven test amplification for pygraphistry features. Use when hardening a feature area via user-workflow exploration, 5-Whys retrospectives, bug-taxonomy derivation, concrete test planning, implementation, and safety-gated validation.

Create and maintain an opt-in, file-based task plan for explicitly planned, multi-session, handoff, or multi-PR work. Use when durable execution state matters; prefer native planning for ordinary single-session work.

Review a pull request, branch, or proposed fix for specification conformance, correctness, tests, security, maintainability, and repository conventions. Use before making a fix or when preparing evidence-backed PR findings; discover applicable specification…

Use for multi-step work that benefits from a short, durable task plan or handoff. Do not require a plan file for routine, single-session changes.

Review a pull request or branch for spec fit, correctness, security, tests, and repository conventions. Use parallel, narrowly scoped analysis and isolated adversarial checks before reporting evidence-backed findings.

OPT-IN file-based planning for multi-session tasks. Only use when user explicitly requests it or work spans multiple sessions. For single-session work, prefer your platform's native planning features.

Input — a PR number / branch (default: current branch's PR). Output — findings.md under plans/<task>/ + optional inline PR comments. Result — multi-wave review converged across spec, correctness, tests, security, credentials, quality, DRY, concurrency,…