postman-weaviate

This MCP server is generated from Postman requests and outputs an MCP-compatible server in mcpServer.js along with JavaScript tools for each selected Postman API. It is configured to run in Node.js environments and exposes tools that you can connect to via MCP clients like Claude Desktop or other MCP-enabled interfaces. The server uses fetch to perform HTTP requests, so ensure your Node version includes fetch (Node 18+ is recommended). You can inspect the generated tools under the tools directory to see how each API request is wired into a reusable function, including how workspace-scoped API keys are injected through environment variables in your .env file.

To test locally, run the server with Node and then connect an MCP client. The server will present the list of tools you selected when you query it through the MCP interface. You can also enable Server-Sent Events (SSE) by starting the server with the --sse flag if you need streaming capabilities for tool outputs.

Prerequisites:

• Node.js v18+ (v20+ recommended)
• npm (comes with Node)

1. Install dependencies From your project root, install the required Node modules:

npm install

2. Prepare environment variables Create a .env file in the project root and add keys for the workspaces/tools you selected. For example:

ACME_API_KEY=
WIDGETS_API_KEY=

These keys are accessed by the generated tool files via process.env and injected into requests as needed. If your API uses a different authentication scheme, adjust the tool files accordingly.

3. Run the MCP server

node mcpServer.js

4. Optional: test with SSE

node mcpServer.js --sse

5. Optional: Docker deployment

• Build image:

docker build -t agentesq-postman-weaviate-mcp-server .

• Run container:

docker run -i --rm --env-file=.env agentesq-postman-weaviate-mcp-server

If you need to connect via Claude or another MCP client, point the client to the absolute path of the node executable and the mcpServer.js file as described in the README.

Tips and common considerations:

• Ensure you are running Node 18+ to have fetch available globally. If you must run on an older Node, you may need to polyfill fetch by installing node-fetch and wiring it as global fetch in your tools.
• When integrating with Claude Desktop, supply absolute paths to the node executable and the mcpServer.js file to avoid version mismatch issues that could disable fetch.
• If you modify authentication or add new APIs, update the .env file accordingly and ensure any new environment variables are used in the corresponding tool files.
• For production deployments, consider using the provided Docker setup and mount an .env file with all necessary variables. The Dockerfile in the README demonstrates a minimal production-ready image.
• If you encounter issues with environment variable naming, remember that the generator creates a variable per workspace slug; you can adjust names in the .env file or tool files to align with your authentication flow.