Install
Volley ships as an npm package. Add it to any MCP-capable client and every agent you run gets a full API testing toolkit — no GUI, no copy-paste, no context bloat.
Option 1: npx (recommended)
The simplest setup. Your MCP client runs npx -y @thupham/volley-mcp which downloads the latest version on first use and caches it. No global install needed.
{
"mcpServers": {
"volley": {
"command": "npx",
"args": ["-y", "@thupham/volley-mcp"]
}
}
}Option 2: global install
Install once, reference the binary directly:
npm install -g @thupham/volley-mcp
# then in your MCP client config:
{
"mcpServers": {
"volley": {
"command": "volley-mcp"
}
}
}Client config file locations
- Cursor —
~/.cursor/mcp.jsonor project.cursor/mcp.json - Windsurf —
~/.codeium/windsurf/mcp_config.json - Claude Desktop —
~/Library/Application Support/Claude/claude_desktop_config.json - Devin CLI —
~/.config/devin/config.json - VS Code —
~/.vscode/mcp.jsonor project.vscode/mcp.json
Verify the connection
Restart your client and ask the agent to list available tools. You should seehttp_request, graphql_request, ws_session,sse_session, inspect_response, and the rest of the surface described in MCP tools.
Tip: thebinname isvolley-mcp. When you runnpx -y @thupham/volley-mcp, npx invokes thevolley-mcpbinary automatically.
From source (development)
If you want to hack on Volley itself or run a local build:
git clone <repo>
cd volley
pnpm install
pnpm build # builds the Rust core, then the TS serverThen point your MCP client at the local build:
{
"mcpServers": {
"volley": {
"command": "node",
"args": ["/absolute/path/to/volley/packages/mcp-server/dist/index.js"]
}
}
}End-to-end verification
To confirm the full pipeline locally without an MCP client, run the bundled e2e script:
pnpm build
pnpm e2e # spins up a local test server and drives every tool over stdioThe script runs 31 checks covering every shipped tool. If it passes, your build is ready to register with any MCP client.