-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Bug Description
MacBook-Pro ~ % npx @toolprint/mcp-graphql-forge --transport http --port 3001
file:///Users/ben/.npm/_npx/2f1cf08851fa3846/node_modules/@toolprint/mcp-graphql-forge/dist/bin.js:5
logger.error('Failed to start MCP GraphQL Forge:', err.message);
^
TypeError: logger.error is not a function
at file:///Users/ben/.npm/_npx/2f1cf08851fa3846/node_modules/@toolprint/mcp-graphql-forge/dist/bin.js:5:12
Node.js v20.19.4
Did this with node 22x as well.
Steps to Reproduce
- Just the steps in the readme. npx @smithery/cli install @toolprint/mcp-graphql-forge --client claude
- GRAPHQL_ENDPOINT="https://your-api.com/graphql" npx -y @toolprint/mcp-graphql-forge --transport http --port 3001
Also tried with existing endpoint and got the same issue
GRAPHQL_ENDPOINT="https://spacex-production.up.railway.app/" npx @toolprint/mcp-graphql-forge --transport http --port 3001
file:///Users/ben/.npm/_npx/2f1cf08851fa3846/node_modules/@toolprint/mcp-graphql-forge/dist/bin.js:5
logger.error('Failed to start MCP GraphQL Forge:', err.message);
^
TypeError: logger.error is not a function
at file:///Users/ben/.npm/_npx/2f1cf08851fa3846/node_modules/@toolprint/mcp-graphql-forge/dist/bin.js:5:12
Node.js v20.19.4
Expected Behavior
It should probably launch and not crash I imagine
Actual Behavior
It crashed
Error Logs
Version
0.1.1
Transport Mode
HTTP
Node.js Version
Node.js v20.19.4
Operating System
Mac OS Seq 15.6.1
GraphQL Endpoint Info
No response
Additional Context
No response
Checklist
- I have searched existing issues to make sure this is not a duplicate
- I have included all relevant information above
- I have removed any sensitive information (tokens, passwords, etc.)