Koskamo

BlockRazor Docs MCP

A documentation-only MCP server that allows AI agents to search and retrieve current BlockRazor integration guides, API references, and source-linked answers from official documentation indexes without requiring authentication.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

BlockRazor Docs MCP logo, by BlockRazorVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by BlockRazor
MCP endpoint (Streamable HTTP)
https://mcp.blockrazor.io/docs
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Can change data (1)

4 of 4 have a description · 4 of 4 declare behavior hints · 3 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to blockrazor.io ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search current BlockRazor documentation
  • Retrieve API references for integration
  • Access source-linked answers for product discovery

Source and maintenance

Vendor evidenceRegistry 1.0.1

Protocol and capabilities

Server
docs.blockrazor.io/~gitbook/mcp 0.28.0
MCP protocol negotiated in check
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

4 advertised

searchDocumentation
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about BlockRazor, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

searchDocumentation input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
searchDocumentation annotations
{
  "title": "Search documentation",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
getPage
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Fetch the full markdown content of a specific documentation page from BlockRazor. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. https://docs.blockrazor.io/getting-started). Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.

getPage input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The URL of the page to fetch"
    }
  },
  "additionalProperties": false
}
getPage annotations
{
  "title": "Get page content",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
askQuestion
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Ask a natural-language question about BlockRazor and get a synthesized answer, with links to the source pages. Prefer this over `searchDocumentation` when you want a direct answer to a question rather than a list of matching pages; use `searchDocumentation`/`getPage` when you need to browse or read full pages yourself.

askQuestion input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "question"
  ],
  "properties": {
    "goal": {
      "type": "string",
      "description": "The broader end goal you are ultimately trying to accomplish (as/on behalf of the user). Used to tailor the answer to be most useful for your goal. Optional."
    },
    "question": {
      "type": "string",
      "description": "The natural-language question to answer about BlockRazor."
    }
  },
  "additionalProperties": false
}
askQuestion annotations
{
  "title": "Ask a question",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}
sendFeedback
Advertised by the server during the last successful anonymous check.
Open-world

Report an issue in the documentation of BlockRazor so the team can fix it. Use it whenever, while helping a user, you come across content that is outdated, contradictory, missing information, or otherwise unhelpful. Also use it when the user themselves reports a problem with the docs, even if you could not verify it yourself. If it's your own observation, do a quick sanity check that the issue is real before reporting — no need to exhaustively re-read the page. Send one call per distinct issue and do not report the same issue twice in a conversation. Do not use this tool to confirm that a page is accurate; it is for reporting problems only.

sendFeedback input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "content",
    "pageUrl"
  ],
  "properties": {
    "goal": {
      "type": "string",
      "maxLength": 1024,
      "description": "The broader end goal you were ultimately trying to accomplish (as/on behalf of the user) when you hit this issue. Gives the team the context you were working towards. Optional."
    },
    "content": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "Explain the issue in full, as if writing to a documentation maintainer who never saw this conversation. Describe what is wrong, where on the page it appears (quote the exact sentence or section title when possible), what the user was trying to do, and, when relevant, what the correct or expected information should be. Write a few clear, specific sentences in English. Never include personal or confidential information from the conversation. Up to 2048 characters."
    },
    "pageUrl": {
      "type": "string",
      "description": "The full URL of the page the issue is about (e.g. https://docs.blockrazor.io/getting-started), so the finding is linked to the exact page."
    }
  },
  "additionalProperties": false
}
sendFeedback annotations
{
  "title": "Send feedback",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1206 ms
95th percentile latency
1206 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1206 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http blockrazor-docs-mcp https://mcp.blockrazor.io/docs

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add blockrazor-docs-mcp --url https://mcp.blockrazor.io/docs

Cursor

Merge this server into .cursor/mcp.json in your project, then enable blockrazor-docs-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "blockrazor-docs-mcp": {
      "url": "https://mcp.blockrazor.io/docs"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "blockrazor-docs-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.blockrazor.io/docs",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start blockrazor-docs-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "blockrazor-docs-mcp": {
      "type": "http",
      "url": "https://mcp.blockrazor.io/docs"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http blockrazor-docs-mcp https://mcp.blockrazor.io/docs

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.blockrazor.io/docs

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "blockrazor-docs-mcp": {
      "serverUrl": "https://mcp.blockrazor.io/docs"
    }
  }
}

Let your agent find its tools

Find servers like BlockRazor Docs MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run BlockRazor Docs MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing