Documentation / MCP servers

From npx to your first tool call.

Choose a package, add one stdio entry to your MCP client, and try it without a license key. This hub stays high-level; every package page contains that server's exact tools, parameters, examples, plan boundaries, and configuration.

10 packages Node.js 18+ stdio by default
Start the quickstart Browse all packages

01 / Quickstart

A concrete stdio setup

The example uses Schema Designer. Replace its server label and npm package with the exact values shown on the package page you choose.

npx

Run the package

All ten packages require Node.js 18 or newer. npx -y downloads and starts the published package without a global install. 

 npx -y mcp-schema-designer
MCP config

Add a stdio entry

Put this shape in the MCP configuration location documented by your client. The client launches the process and exchanges MCP messages over standard input and output. 

{
  "mcpServers": {
    "schema-designer": {
      "command": "npx",
      "args": ["-y", "mcp-schema-designer"]
    }
  }
}
First call

List, then call a tool

Restart or reload your client, confirm the server's tools appear, and invoke one. Tool calls—not merely starting the stdio process—are what pass through the package's license and trial check. 

List the schema-designer tools.

Design a PostgreSQL schema for a small issue tracker.

Where each client keeps its config

The three file-based clients accept the same mcpServers object; only the file path differs. Claude Code takes a command instead of a file.

  • Claude Desktop ~/Library/Application Support/Claude/claude_desktop_config.json

    Windows: %APPDATA%\Claude\claude_desktop_config.json. In the app: Settings → Developer → Edit Config.

  • Cursor ~/.cursor/mcp.json

    Or .cursor/mcp.json inside a single project.

  • Windsurf ~/.codeium/windsurf/mcp_config.json

    Cascade panel → MCP icon → edit the raw config.

Using Claude Code? One command, no file

Claude Code
$ claude mcp add --transport stdio schema-designer -- npx -y mcp-schema-designer

Confirm it registered with claude mcp list. Add a key later with --env LICENSE_KEY=your-key placed before --transport. Common licensing questions are answered on the FAQ.

02 / License lifecycle

Purchase, configure, recover

License keys are product-bound and plan-aware. Treat both a key and its Stripe Checkout session link as private credentials.

Checkout

Read the return page

A paid Checkout is configured to return with a session ID to the success page. That page asks the server to confirm the payment and known product before rendering a key. Opening the bare page without its Checkout session cannot retrieve one.

Configuration

Use the package's exact entry

The generic trial snippet intentionally has no guessed license variable. After purchase, copy the setup block shown with the key or follow that package page. The current npm package docs use LICENSE_KEY in the server's env object. Never commit the key.

Support

Keep the Checkout link

Bookmark the Checkout return URL; its session ID is the input used by the working-tree recovery flow. Retain the receipt separately in case manual support is ever required.

Activate a purchased key, end to end

  1. Buy the plan from the product card on the home page (Stripe Checkout).
  2. Copy the key shown on screen on the success page once Stripe reports the payment as paid — that page is the authoritative copy of your key, so copy or bookmark it there. Email is a secondary channel: it is not available today (the sending domain is unverified) and delivery is never guaranteed, so do not wait for an email.
  3. Paste it into that server's env block as LICENSE_KEY (shown below).
  4. Restart the client so it reloads the config and starts the server with the key.
  5. Verify by calling a tool the trial had blocked, or run claude mcp list in Claude Code and look for ✔ Connected.
mcpServers entry with license
{
  "mcpServers": {
    "schema-designer": {
      "command": "npx",
      "args": ["-y", "mcp-schema-designer"],
      "env": {
        "LICENSE_KEY": "paste-your-key-here"
      }
    }
  }
}

Keys are valid for 365 days and verify offline against a public key compiled into the package — no account, no network check, no usage reporting. Plans bill monthly, but the key carries a fixed 365-day expiry and has no revocation mechanism: cancelling stops future charges and does not switch the key off. Lost the key? Recover it here. More detail on the FAQ.

03 / Package reference

Choose the server that owns the job

These summaries come from the checked-in package sources. Open a package page for its authoritative npm name, exact tool schemas and parameters, usage examples, data-source notes, and current plan split.

Developer tools · 5 tools

AI Cost Analyzer

Analyze supplied LLM usage, estimate savings, reduce prompt overhead, compare model cost tradeoffs, and inspect its bundled model-pricing table.

Tools: analyze_usage, estimate_savings, optimize_prompt, compare_models, get_pricing

AI Cost Analyzer docs
Developer tools · 5 tools

MCP Security Scanner

Inspect MCP configurations and tool definitions, check a built-in CVE catalog, validate auth settings, and turn scan results into a Markdown report.

Tools: scan_config, scan_tool_definitions, check_cves, validate_auth, generate_report

Security Scanner docs
Data utilities · 6 tools

Data Aggregator

Query stocks and crypto, fetch webpages, search news, look up weather and exchange rates, and access selected public-data utilities from one server.

Tools: query_stocks, fetch_webpage, search_news, query_weather, query_exchange_rates, query_public_data

Data Aggregator docs
Finance · 6 tools

Market Data Analyzer

Analyze stocks, screen a built-in universe, evaluate portfolios, compare assets, view a market snapshot, and inspect crypto using Yahoo Finance and CoinGecko data.

Tools: analyze_stock, screen_stocks, analyze_portfolio, compare_assets, market_overview, crypto_analysis

Market Data Analyzer docs
Marketing · 5 tools

SEO Audit Tool

Audit a live page, analyze supplied text for keywords, check page links, validate an XML sitemap, and compare two pages without an external API key.

Tools: audit_page, analyze_keywords, check_links, analyze_sitemap, compare_pages

SEO Audit Tool docs
Developer tools · 5 tools

Schema Designer

Design and validate PostgreSQL schemas, generate migration SQL and typed outputs, and review queries. It generates artifacts; it does not connect to or modify a database.

Tools: design_schema, validate_schema, migrate_schema, generate_types, optimize_queries

Schema Designer docs
Marketing · 5 tools

Social Media Analytics

Attempt basic public-profile scraping with a documented deterministic estimate fallback, research hashtags, generate content calendars, compare competitors, and score post concepts heuristically.

Tools: analyze_profile, analyze_hashtags, generate_content_calendar, analyze_competitors, viral_score

Social Media Analytics docs
Career · 6 tools

Resume Optimizer

Score resume text, match it to a job description, analyze keywords, draft professional summaries, strengthen bullets, and run ATS-oriented checks using local text heuristics.

Tools: analyze_resume, optimize_for_job, generate_summary, improve_bullets, check_ats, analyze_keywords

Resume Optimizer docs
Legal · 5 tools

Legal Doc Analyzer

Apply local text and pattern analysis to contracts for terms, risks, version changes, summaries, and selected compliance checks. It is informational, not legal advice.

Tools: analyze_contract, find_risks, compare_versions, generate_summary, check_compliance

Legal Doc Analyzer docs
Developer tools · 5 tools

API Doc Generator

Generate OpenAPI 3.1 output, endpoint documentation, a TypeScript SDK, validation findings, and Jest or Vitest test suites from endpoint definitions.

Tools: generate_openapi, document_endpoint, generate_sdk, validate_api, generate_tests

API Doc Generator docs

04 / Reference paths

Human-readable and machine-readable

Use the format that matches the question: comparison for selection, package pages for implementation, and plain text for automated discovery.

Selection

Compare all ten

See the packages side by side before opening the detailed reference for a shortlist.

Open comparison
Plain text

Give an agent a clean index

Start with the concise llms.txt catalog, or use llms-full.txt when the expanded package reference is useful.

License utilities

Return and recovery pages

The success page is the Checkout return target and requires its session query parameter. The recovery page is the working-tree self-service flow described above.