About fleetstreet
fleetstreet CLI lets platform operators manage creator tenants, revenue, support, AI licensing, and compliance. Its creator-scoped remote MCP server provides agents with a read-only view of creators’ compliance data.
Key features
- 01Tenant and user dashboard
- 02Revenue and signup funnel metrics
- 03Tenant and support ticket management
- 04Register works and manage AI licenses
- 05Compliance assessments and audit exports
Use cases
- 01Review platform activity and revenue
- 02Manage tenant access and support tickets
- 03Issue or revoke AI licenses for creative works
- 04Review creator compliance evidence
MCP support
The remote server at mcp.fleetstreet.ai exposes 46 tools. Creator-authenticated agents receive read-only tools for compliance posture, frameworks, audit events, and exports.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.fleetstreet.ai/sseclaude mcp add --transport sse jyswee-fleetstreet https://mcp.fleetstreet.ai/sse{"mcpServers":{"jyswee-fleetstreet":{"type":"sse","url":"https://mcp.fleetstreet.ai/sse"}}}Open in Cursor{"servers":{"jyswee-fleetstreet":{"type":"sse","url":"https://mcp.fleetstreet.ai/sse"}}}Open in VS Code{"mcpServers":{"jyswee-fleetstreet":{"type":"sse","url":"https://mcp.fleetstreet.ai/sse"}}}{"mcpServers":{"jyswee-fleetstreet":{"serverUrl":"https://mcp.fleetstreet.ai/sse"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp.fleetstreet.ai/sseAuth requiredTools
Details
From the project READMEfst
Platform management for fleetstreet — license your creative work to AI, on your terms. Tenant admin, analytics, AI licensing, compliance evidence, support tickets - from the terminal.
Install
npm install -g fleetstreet-cli
Quick Start
# 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 [email protected] --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.
Config
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
Local config overrides global. Add .fst/ to your .gitignore.
Agent Integration
Add to your CLAUDE.md or agent instructions:
## fleetstreet Admin
Use the fst CLI for platform management.
Key is in .fst/config.json (auto-loaded).
Run fst --help for full reference.
JSON Output
All commands support --json for machine-readable output:
fst stats --json
fst tenants --json
fst tickets --json
Documentation
License
Proprietary - Tyga.Cloud Ltd. See LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.