CLI tool to run Whatsease MCP server from OpenAPI spec
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"whatsease-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Whatsease MCP CLI tool to run a Model Context Protocol (MCP) server for the Whatsease API. ## Installation ```bash pip install whatsease-mcp ``` ## Usage ### Basic Usage ```bash whatsease-mcp --api-url https://api.whatsease.com ``` Or using environment variable: ```bash export WHATSEASE_API_BASE_URL=https://api.whatsease.com whatsease-mcp ``` ### Options | Option | Short | Default | Description | | ------------------ | ----- | ---------------- | ---------------------------------- | | `--api-url` | `-u` | (required) | Base URL of the Whatsease API | | `--port` | `-p` | `8001` | Port to run the MCP server on | | `--host` | `-h` | `0.0.0.0` | Host to bind the MCP server to | | `--include-config` | `-c` | `./include.json` | Path to include.json config file | | `--transport` | `-t` | `http` | Transport type (`http` or `stdio`) | ### Examples ```bash # Run on custom port whatsease-mcp -u https://api.whatsease.com -p 8080 # Run on localhost only whatsease-mcp -u https://api.whatsease.com -h localhost # Use stdio transport (for direct MCP client integration) whatsease-mcp -u https://api.whatsease.com -t stdio # Use custom config file whatsease-mcp -u https://api.whatsease.com -c /path/to/include.json ``` ## Configuration ### include.json Create an `include.json` file to control which API routes are exposed as MCP tools. **Default behavior (no config or empty config):** All routes from the OpenAPI spec are exposed. **With config:** Only matching routes are exposed, plus a catch-all exclude at the end. #### Format ```json { "include": [ { "mcp_type": "TOOL", "methods": ["GET", "POST"], "pattern": "/platforms/.*" }, { "mcp_type": "TOOL", "methods": ["GET"], "pattern": "/templates/.*" } ] } ``` #### Fields | Field…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.