This is an automated email from the ASF dual-hosted git repository.

spmallette pushed a commit to branch gremlin-mcp
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git

commit 2ed68a5cb537a6c3b5bfe9067aec17168499ce82
Author: Stephen Mallette <[email protected]>
AuthorDate: Wed Oct 1 14:40:52 2025 -0400

    Added point about testing gremlin-mcp to dev docs
---
 docs/src/dev/developer/development-environment.asciidoc | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/src/dev/developer/development-environment.asciidoc 
b/docs/src/dev/developer/development-environment.asciidoc
index f8b804e709..920a78a3cb 100644
--- a/docs/src/dev/developer/development-environment.asciidoc
+++ b/docs/src/dev/developer/development-environment.asciidoc
@@ -319,6 +319,16 @@ built. Consequently, the scripts `bin/generate-home.sh` 
and `bin/publish-home.sh
 installed. Check the root `pom.xml` for the `runtime.node.version` property 
for the minimum version required. This is
 covered in more detail in the <<site,Site>> section.
 
+A fast way to test `grelin-mcp` after doing a build is to use 
link:https://modelcontextprotocol.io/docs/tools/inspector[@modelcontextprotocol/inspector]
+which will start up the Gremlin MCP server and present a browser-based tool to 
use the commands. It is most easily
+launched with `npx` as follows:
+
+[source,text]
+----
+# from the root of the repository
+$ npx @modelcontextprotocol/inspector node 
gremlin-mcp/src/main/javascript/dist/server.js -e 
GREMLIN_ENDPOINT=localhost:8182/g -e LOG_LEVEL=info
+----
+
 IMPORTANT: Beware of unexpected or unwanted changes on `package-lock.json` 
files when committing and merging.
 
 TIP: For those who do not have a full Maven environment, please see 
<<docker-integration,this section>> for how Docker

Reply via email to