Get the FREE Ultimate OpenClaw Setup Guide →

mcp-whats-the-passphrase

Example node MCP server. When a user asks the agent for the passphrase, a special code phase is provided.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio gbti-network-mcp-whats-the-passphrase npx --yes node <path-to-project>/index.js

How to use

This MCP server is a pure Node.js implementation that exposes a single tool called getSecretPassphrase. The server runs using the MCP protocol over STDIO and is designed to be tested with the MCP Inspector. To start it, connect via MCP Inspector and launch the server using the npx wrapper described in the installation notes. Once running, you can invoke the getSecretPassphrase tool to obtain a random State + soup combination. The tool adheres to a strict input schema (an empty object) and returns a JSON structure containing the generated content as an array of text elements, for example a single item like New England Clam Chowder. You can integrate this tool into Cascade or other natural language interfaces by routing queries to getSecretPassphrase and composing the response into a user-friendly phrase such as Today's secret passcode is: Louisiana Gumbo.

How to install

Prerequisites:

  • Node.js (LTS recommended)
  • npm (comes with Node.js)
  • MCP Inspector (for testing)

Installation steps:

  1. Clone the repository git clone git@github.com:gbti-network/mcp-basic-test.git cd mcp-basic-test

  2. Install dependencies npm install

  3. Run with MCP Inspector npx @modelcontextprotocol/inspector -- node index.js

Notes:

  • The server exposes the getSecretPassphrase tool via the MCP protocol. Ensure MCP Inspector is configured to connect over STDIO as shown above.
  • You can also configure mcp_config.json in Cascade using the npx command wrapper provided in this document when testing in that environment.

Additional notes

Tips and tips:

  • The server uses a custom logger and writes logs to the .logs directory; check these files if you encounter issues.
  • If you add new tools, register them in index.js with the same pattern used in the development section to ensure MCP Inspector can list and execute them.
  • Input schemas are intentionally minimal for the getSecretPassphrase tool; even though the example shows an empty object, ensure you send the exact schema defined for each tool to avoid validation errors.
  • When integrating with Cascade, you can configure autoApprove for getSecretPassphrase to streamline testing; adjust mcp_config.json accordingly.
  • Environment-specific issues (path resolution, Node.js version mismatches) are common; ensure <path-to-project> in the mcp_config points to the correct project root when using a wrapper script.

Related MCP Servers

Sponsor this space

Reach thousands of developers