Skip to content

Release v1.0.4

Latest
Latest

Choose a tag to compare

View all tags
@chengbiao-jin chengbiao-jin released this 05 Oct 23:23
· 2 commits to main since this release
v1.0.4
f560caa
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

tigergraph-mcp 1.0.4 Release Notes

This release makes the server installable from Claude Code in two commands and discoverable through the official MCP Registry, and gives agents more control over the queries they run.

New

  • Install from Claude Code as a plugin — claude plugin marketplace add tigergraph/tigergraph-mcp followed by claude plugin install tigergraph@tigergraph replaces installing the package, writing a .env file, and hand-writing an MCP client configuration. Claude Code prompts for the TigerGraph host and credentials and keeps the password and API token in secure storage rather than in a file on disk.
  • Listed in the official MCP Registry — MCP clients and directories that read the registry can now discover and install the server by name.

Changed

  • Interpreted queries accept parameters — run_query can now supply values for the parameters a query declares, so an agent no longer has to write values into the query text.
  • Installed queries can be bounded — run_installed_query can set a timeout, a response size limit, and thread and memory limits, and can choose a replica. Previously a long-running query could only run within the server's default timeout, and nothing capped what it consumed.

Bug Fixes

  • Vertex IDs containing a double quote — get_neighbors and get_node_degree failed on such an ID, and text after the quote was run as GSQL. Any vertex ID is now handled correctly, and invalid vertex or edge type names are rejected before anything runs.
  • Reported server version — MCP clients were shown the SDK's version, or an empty string, instead of the tigergraph-mcp version. Clients now see the actual release, so a session can be traced to the version it connected to.

Upgrading

No action required for pip or conda installs.

  • pyTigerGraph 2.0.5 or later is now required (was 2.0.4). Upgrading tigergraph-mcp pulls it in automatically; environments that pin pyTigerGraph need to raise the pin. Earlier versions garble query parameter values that contain spaces, quotes, &, %, #, or non-ASCII characters.
  • The plugin requires uv on the PATH, because it launches the server with uvx. Installing the package directly remains an option for machines without uv.
  • Permission rules for the plugin — in permission rules, a skill's allowed-tools, or a hook matcher, the plugin's server is named plugin:tigergraph:tigergraph. A pattern such as mcp__tigergraph__.* does not match a plugin-provided server.

Full Changelog

v1.0.3...v1.0.4

Assets 2
Loading