For AI systems & developers
BluSup speaks MCP.
BluSup provides a small, read-only Model Context Protocol doorway into its public information. Compatible AI clients can orient themselves, discover BluSup's explicit agent boundaries, search public BluSup content, and fetch a selected public result without receiving owner, admin, PIN, upload, delete, or private-data access.
https://blusup.com/mcp/
Modern protocol version: 2026-07-28
Available tools
Recommended flow
describe_blusup → search_blusup → fetch_blusup_result
The endpoint uses JSON-RPC over HTTP POST and is intended for MCP-capable clients rather than ordinary browser navigation.
Browser-readable bridge: AI systems that can browse the web but cannot speak MCP directly can read the same public-safe operational data through Live Status and Live Team Notes.
Public-safe by design
- Read-only access
- Public BluSup information only
- No owner or admin actions
- No PIN or login elevation
- No private My Blog content
Quick client setup
Here is a simple copy-and-paste configuration block you can adapt in an MCP-capable client. Different clients may use different keys, but the endpoint and intent remain the same.
MCP test bench
Use the quick buttons to build a request, adjust it if you want, then run it against the live BluSup MCP endpoint. This is all browser-side and same-origin.
Tip: use Status for the current sanitized BluSup status, or run Search first and then paste one exact returned URL into the fetch box and run Fetch.
Run a request to see the BluSup MCP response here.