io.github.jyswee/fleetstreet MCP Server

This MCP server provides command-line platform management for Fleetstreet, focused on licensing creative work to AI on defined terms. It supports tenant administration, analytics, AI licensing, compliance evidence, and support ticket operations, all from the terminal. The server is described as “46 tools” and “keyless,” with CLI-based usage.

🛠️ Key Features

Platform management for fleetstreet
Tenant admin
Analytics (e.g., stats, revenue metrics, signup funnel)
AI licensing
Compliance evidence
Support tickets (list and view)

🚀 Use Cases

Manage multiple tenants (list tenants, view a tenant by ID)
Check operational and revenue-related metrics from the terminal
Handle support requests by viewing tickets and ticket details

⚡ Developer Benefits

Terminal-based access to platform functions
Example commands for login, dashboard stats, revenue, funnel, tenants, and tickets

⚠️ Limitations

Tooling count in source data is inconsistent (“46 tools” vs. toolCount: 2), so exact MCP tool coverage cannot be confirmed from the provided excerpt.

{ "type": "object", "properties": { "bandName": { "type": "string", "description": "The portfolio / studio / artist name, e.g. \"Jane Doe Photography\". Used as the site name and to derive the slug." }, "email": { "type": "string", "description": "Human email. The welcome + activation link is sent here." }, "firstName": { "type": "string", "description": "The human's first name (optional; used to personalise the welcome email)." }, "genre": { "type": "string", "description": "Optional discipline (photography, illustration, mixed-media, …)." } }, "required": [ "bandName", "email" ] }

Quick Start

bash

# Login with your SuperAdmin API key
fst login --key YOUR_SA_API_KEY

# Platform dashboard
fst stats

# Revenue metrics
fst revenue

# Signup funnel
fst funnel

# List all tenants
fst tenants

# View a tenant
fst tenant show TENANT_ID

# Support tickets
fst tickets
fst ticket show TKT-abc123

# Chat with τAI h-conductor
fst tai "show me open P0 bugs" --dept dev

# AI Licensing (A2A copyright moat)
fst licensing harbourlight               # licensing overview for a creator
fst licensing harbourlight register ID   # register a work (image, writing, video, or track)
fst licensing harbourlight issue ID      # issue a scoped AI licence (view|derivative|train)
fst licensing harbourlight access-log    # provable access log (granted + blocked)

# Video works (footage)
fst videos harbourlight                  # list video works
fst videos harbourlight create "Title" --set videoUrl=https://...  # create (then register + license)

# Voice consent registry (voice works)
fst voice-consents harbourlight          # list actor consents
fst voice-consents harbourlight create --actor "Name" --email a@x.com --scopes read,summarise
fst voice-consents harbourlight revoke ID --reason "..."   # blocks future licence issuance

# Compliance evidence
fst compliance                           # snapshot (posture + frameworks + A2A events)
fst compliance posture                   # CISO posture score (0-100)
fst compliance frameworks eu-ai-act      # framework assessment
fst compliance audit-events --filter blocked
fst compliance export --format json      # export the OCSF audit log

# Full reference
fst help

Features

Dashboard - tenant counts, user stats, post/order totals

Revenue - MRR, ARR, platform fees, payouts

Funnel - signup → verified ($1) → active → paying

Tenants - list, view, suspend, activate

Support - tickets, reply, close

τAI Chat - talk to h-conductor (6 departments: dev, devops, bizintel, compliance, helpdesk, fixer)

AI Licensing - register works (images, writing, music), issue/revoke per-use AI licences, provable access log (the A2A copyright moat)

Compliance - posture score, framework assessment (EU AI Act, NIST AI RMF, SOC 2, Colorado SB24-205, GDPR), OCSF audit-event stream + export

Compliance-for-agents parity

The same AI-licensing and compliance surface is exposed to per-creator agents over the remote MCP server (mcp.fleetstreet.ai, v1.3.1, 46 tools). An agent authenticated with a creator-scoped fsk_ key gets read-only fleetstreet_compliance, fleetstreet_compliance_posture, fleetstreet_compliance_frameworks, fleetstreet_compliance_audit_events and fleetstreet_compliance_export tools — a per-creator mirror of the fst compliance commands here (which run platform-wide via the SuperAdmin API). Same evidence, two front doors: this CLI for platform operators, the remote MCP for a creator's own agent.

fst login --local --key YOUR_KEY # saves to .fst/config.json (project-local) fst login --key YOUR_KEY # saves to ~/.fst/config.json (global) fst config # show which config is active

Install

Tools (2)

fleetstreet_get_startedfleetstreet_signup

Remote endpoint

SSE

Hosted server - connect over the network, no local install.

url

https://mcp.fleetstreet.ai/sse

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "fleetstreet": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fleetstreet.ai/sse"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

io.github.jyswee/fleetstreet