Skip to main content

Whatsease MCP

CLI tool to run a Model Context Protocol (MCP) server for the Whatsease API.

Installation

pip install whatsease-mcp

Usage

Basic Usage

whatsease-mcp --api-url https://api.whatsease.com

Or using environment variable:

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

# 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

{
    "include": [
        {
            "mcp_type": "TOOL",
            "methods": ["GET", "POST"],
            "pattern": "/platforms/.*"
        },
        {
            "mcp_type": "TOOL",
            "methods": ["GET"],
            "pattern": "/templates/.*"
        }
    ]
}

Fields

Field Type Description
mcp_type string One of: TOOL, RESOURCE, RESOURCE_TEMPLATE, EXCLUDE
methods array HTTP methods to match: GET, POST, PUT, DELETE
pattern string Regex pattern to match route paths

Example Configurations

Expose only GET routes:

{
    "include": [
        {
            "mcp_type": "TOOL",
            "methods": ["GET"],
            "pattern": ".*"
        }
    ]
}

Expose specific endpoints:

{
    "include": [
        {
            "mcp_type": "TOOL",
            "methods": ["GET", "POST"],
            "pattern": "^/platforms/.*"
        },
        {
            "mcp_type": "TOOL",
            "methods": ["GET"],
            "pattern": "^/templates/.*"
        },
        {
            "mcp_type": "TOOL",
            "methods": ["GET", "POST"],
            "pattern": "^/campaigns/.*"
        }
    ]
}

License

MIT

Metadata

Release files for whatsease-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for whatsease-mcp 0.1.0
File Size Uploaded Provenance
whatsease_mcp-0.1.0.tar.gz 4.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for whatsease-mcp 0.1.0
File Interpreter ABI Platform
whatsease_mcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 10.5 kB

Release files / whatsease_mcp-0.1.0.tar.gz

Download URL whatsease_mcp-0.1.0.tar.gz
Size 4.7 kB
Tags Source
SHA-256 checksum
How to use checksums
25e74795ce114f0694b9e8c7f29b25004caa4588942657a4588a5f05425aa7c3
BLAKE2b-256 checksum
How to use checksums
c118b0002def754fd5b2eda4ab43417b85aef16739c07c33654281398bad93fb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.6

Release files / whatsease_mcp-0.1.0-py3-none-any.whl

Download URL whatsease_mcp-0.1.0-py3-none-any.whl
Size 5.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
798e8d33308bdeaa060b16944d37e53b565c9786e617d5a07495c99d15cf3806
BLAKE2b-256 checksum
How to use checksums
edc293022d10897534d825bd09f05e26df22f5ba4f2ab76af56ce3941c05bb01
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.6

Security for whatsease-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page