AI Agent Access
This page is available as structured data for AI agents. All resources are static files served from Cloudflare's edge network with 24-hour caching.
- MCP Server
https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/public-mcp- MCP Manifest
https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/mcp.json- Root Directory
https://fosroc.directory.norg.ai/public-mcp- Transport
- Streamable HTTP · MCP 2025-03-26
- WebMCP
- navigator.modelContext tools (Chrome 146+)
- Available Formats
-
Direct HTTP Access
Fetch any resource directly with standard HTTP:
curl https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/index.json # Structured data
curl https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/index.jsonld # Schema.org linked data
curl https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/index.md # LLM-friendly text
curl https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/mcp.json # MCP manifest
MCP Client Configuration
Connect your AI agent to this page's MCP server endpoint:
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"directory": {
"type": "http",
"url": "https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/public-mcp"
}
}
}
ChatGPT
In ChatGPT, go to Settings → Connectors → Create and enter:
Name: directory
URL: https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/public-mcp
OpenAI MCP docs →
Gemini
Add to Gemini CLI settings.json:
{
"mcpServers": {
"directory": {
"httpUrl": "https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/public-mcp"
}
}
}
Claude Code
claude mcp add directory \
--transport http https://fosroc.directory.norg.ai/construction-materials/concrete-repair-patching/public-mcp
How it works
Each page is pre-rendered in multiple formats and published to Cloudflare R2. The MCP server speaks JSON-RPC 2.0 over Streamable HTTP, backed by edge-cached resources from 300+ locations worldwide.
- Protocol
- MCP 2025-03-26 (Streamable HTTP + Legacy SSE)
- Caching
- Workers KV manifests (24h) + edge-cached content (1h)
- Authentication
- None required — public read-only access