Developer Tools

bliplogger.com

Provides access to BlipLogger configuration and documentation, including installation protocols, API boundaries, and project summaries.

1 endpoint11 known toolsCached registry data

ENDPOINT 1

https://www.bliplogger.com/api/mcp

No auth detected

Known tools 11

read_ai_install_protocol

Returns the BlipLogger AI install protocol: the 12-point agent protocol, installation steps, human approval definition, and what requires explicit human approval.

read_machine_api_boundaries

Returns the BlipLogger Machine API boundaries: what the API accepts (draft entries only), required headers, payload limits, and what not to infer about BlipLogger capabilities.

read_widget_snippet

Returns the canonical and side-panel BlipLogger widget script tags and a post-install verification checklist.

get_governance_boundary_summary

Returns a summary of what is and is not possible via BlipLogger MCP: human approval requirements, what is not live today, and permanently blocked capabilities.

get_project_summary

Returns a summary of the authenticated BlipLogger project: name, slug, visibility, creation date, and entry counts by status.

list_changelog_entries

Returns a paginated list of changelog entries for the authenticated BlipLogger project.

create_changelog_draft

Creates a governed draft changelog entry for the authenticated BlipLogger project.

get_project_install_context

Returns the complete install context for the authenticated BlipLogger project: project id, name, slug, canonical widget snippet with the real project slug, side-panel snippet, MCP endpoint, current authenticated tool list with required scopes, and human approval/governance boundaries.

validate_widget_install_snippet

Validates a submitted widget snippet or page HTML against the authorized BlipLogger project slug.

get_project_widget_runtime_status

Reports the BlipLogger-owned widget runtime status for the authorized project.

get_project_ai_setup_readiness

Reports AI setup readiness for the authorized BlipLogger project: project setup status, available MCP workflows with required scopes, current key capabilities, widget/runtime readiness summary, safe next steps, and hard boundaries.