No tools extracted
Your generation returned tools_count: 0. Here's how to fix it depending on your source type.
OpenAPI — Wrong URL
mcp-forge needs the spec file, not the API base URL.
✗
Wrong:
https://api.stripe.com/
✓
Right:
https://api.stripe.com/openapi.json
Common spec paths to try:
/openapi.json
/swagger.json
/v3/openapi.json
/api-docs
GraphQL — Introspection disabled
Many production GraphQL APIs (GitHub, Shopify, Stripe…) disable introspection for security. mcp-forge cannot generate a server without it.
Solutions
- • Try the dev or staging endpoint, which often has introspection enabled.
- • Use the CLI locally with a saved schema file:
mcp-forge run schema.graphql
Website — JavaScript SPA
mcp-forge analyzes server-rendered HTML by default. SPAs (React, Vue, Angular) require full JavaScript rendering, which needs the CLI.
Solution — run the CLI with Playwright
pip install 'vulcai-mcp-forge-cli[web]' playwright install chromium mcp-forge run <url>
Codebase — No public functions
mcp-forge extracts exported / public functions and methods. Make sure your code exposes at least one.
- • Check that your file contains public functions (not only private/internal ones).
- • For codebases, use the CLI locally — it supports 23 languages including COBOL, Fortran, and Java:
mcp-forge run <path/to/codebase>
Still stuck? Contact us at contact@vulcai.io · Back to home → · Trust & Security