Common Workflows

5 practical examples showing how to analyze APIs, generate servers, secure deployments, and integrate with your development workflow.

Install from Package Managers

Selqor MCP Forge is available on major package registries. Choose your preferred installation source:

NPM REGISTRY

Install via npm

Get selqor-mcp-forge from npm - the official Node.js package repository

View on npm →
PYPI REGISTRY

Install via pip

Get selqor-mcp-forge from PyPI - the official Python package repository

View on PyPI →
1

Analyze an API Specification

Review how a spec will be curated into MCP tools without generating code. Perfect for evaluating which APIs are good candidates for agent access.

Steps

  1. Gather your OpenAPI spec. This can be a file or URL.
  2. Run the analyze command:
    $ selqor-mcp-forge analyze \
      --spec https://api.github.com/openapi.json \
      --output-format json \
      --save-plan ./github-plan.json
  3. Review the plan file to see endpoint groupings, tool counts, and coverage metrics.
✓ Result: You get a detailed JSON plan showing exactly how endpoints will be grouped into intent-based tools, along with quality scores and coverage analysis.
💡 Tip: Use --output-format html to get a visual report in your browser.
2

Generate and Deploy an MCP Server

Convert an API spec into a production-ready MCP server and get it running in minutes. Choose TypeScript or Rust based on your stack.

Steps

  1. Generate the server:
    $ selqor-mcp-forge generate \
      --spec ./stripe-openapi.json \
      --lang typescript \
      --transport stdio \
      --auth api-key \
      --output ./stripe-mcp
  2. Install dependencies:
    $ cd stripe-mcp && npm install
  3. Build and test:
    $ npm run build && npm start
  4. Configure authentication: Set your API key in environment variables or config file.
✓ Result: A fully functional MCP server ready to integrate with Claude, using only the agent-relevant tool set from your spec.
💡 Tip: Use --transport http for web-based clients instead of stdio.
3

Security Scan Before Deployment

Detect vulnerabilities, OWASP issues, and misconfigurations before agents interact with your MCP servers. Generate compliance reports.

Steps

  1. Run security scan:
    $ selqor-mcp-forge scan \
      --spec ./openapi.json \
      --report pdf \
      --output ./security-report.pdf \
      --fail-on-critical
  2. Review the report for critical, high, and medium severity issues.
  3. Fix identified issues in your API or MCP server configuration.
  4. Re-scan to verify all critical issues are resolved.
✓ Result: A compliance-ready PDF report documenting OWASP Agentic Top 10 analysis, CVE checks, and hardening recommendations.
💡 Tip: Integrate the --fail-on-critical flag into your CI/CD to block risky deployments automatically.
4

Multi-Spec Benchmark and Comparison

Compare compression ratios and tool efficiency across multiple APIs. Identify which services compress best and deliver the highest agent value.

Steps

  1. Gather multiple OpenAPI specs. Save them in one directory.
  2. Run benchmark:
    $ selqor-mcp-forge benchmark \
      --specs ./specs/*.json \
      --compare \
      --metrics endpoints,tools,compression-ratio \
      --output ./benchmark-results.json
  3. Analyze results to compare which APIs:
    • Compress most efficiently (e.g., 74→10 tools)
    • Maintain best coverage
    • Are most agent-friendly
  4. Prioritize generation for the best-performing APIs first.
✓ Result: A JSON comparison showing compression metrics, tool counts, and coverage for each API—helping you prioritize which services to integrate.
💡 Tip: This is great for architecture decisions: should we expose GitHub, GitLab, or Gitea? The benchmark tells you which agent integration delivers the best signal-to-noise ratio.
5

CI/CD Integration and Automated Deployment

Automate MCP server generation, scanning, and deployment in your GitHub Actions, GitLab CI, or other CI/CD pipeline.

Steps

  1. Create a CI/CD workflow file:
    # .github/workflows/deploy-mcp.yml
    name: Generate and Deploy MCP Server on: push: paths: - 'openapi.json' workflow_dispatch: jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Install Selqor MCP Forge run: pip install selqor-mcp-forge - name: Analyze spec run: | selqor-mcp-forge analyze \ --spec ./openapi.json \ --output-format json \ --save-plan ./plan.json - name: Security scan run: | selqor-mcp-forge scan \ --spec ./openapi.json \ --report json \ --output ./security-report.json \ --fail-on-critical - name: Generate server run: | selqor-mcp-forge generate \ --spec ./openapi.json \ --lang typescript \ --output ./mcp-server - name: Build and test run: | cd mcp-server npm install npm run build npm test - name: Deploy run: | # Deploy to your hosting (Docker, Lambda, etc.) echo "Deploying MCP server..."
  2. Commit and push your OpenAPI spec or trigger manually.
  3. Monitor the workflow for analysis, security, and build results.
  4. Review artifacts (plan, security report, generated code) in the workflow run.
✓ Result: Every time your API spec changes, your MCP server is automatically analyzed, scanned for security issues, generated, tested, and deployed—with zero manual steps.
💡 Tip: Save the security report and tool plan as workflow artifacts so your team can review them before deployment. Use --fail-on-critical to automatically block risky deployments.

Quick Reference

Common command patterns for quick copy-paste:

Analyze (No Generation)

$ selqor-mcp-forge analyze \
  --spec ./spec.json

Generate (TypeScript)

$ selqor-mcp-forge generate \
  --spec ./spec.json \
  --lang typescript

Security Scan

$ selqor-mcp-forge scan \
  --spec ./spec.json \
  --report pdf

Benchmark

$ selqor-mcp-forge benchmark \
  --specs ./specs/*.json

Dashboard

$ selqor-mcp-forge dashboard \
  --port 8787

Generate + Rust

$ selqor-mcp-forge generate \
  --spec ./spec.json \
  --lang rust

Need More Help?

Explore our documentation and resources:

Installation Guide

Get set up with npm, pip, or source.

View guide →

CLI Reference

All commands with detailed options.

View reference →

Product Overview

Learn about features and capabilities.

Explore product →