INDIVIDUAL MCP TOOL

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.

bliplogger.comnone authenticationAvailability not checked

Input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent endpoint

bliplogger.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bliplogger-com]
url = "https://www.bliplogger.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "bliplogger-com": {
      "type": "http",
      "url": "https://www.bliplogger.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: bliplogger-com
Remote MCP URL: https://www.bliplogger.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bliplogger-com": {
      "url": "https://www.bliplogger.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "bliplogger-com": {
      "type": "http",
      "url": "https://www.bliplogger.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "bliplogger-com",
  "transport": "streamable-http",
  "url": "https://www.bliplogger.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

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_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.