NOTICE MCP Server

🚀 High-performance MCP Server for Crawl4AI - Enable AI assistants to access web scraping, crawling, and deep research via Model Context Protocol. Faster and more efficient than FireCrawl!. The notice mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

This repository maintains a pinned, locally verified distribution of Crawl4AI 0.9.1. It runs the upstream container and its native Model Context Protocol (MCP) server. It is not a custom MCP implementation.

Its toolset

Everything the assistant can do here goes through one of these:

• Server — Sent Events (SSE)**: http://127.0.0.1:11235/mcp/sse
• WebSocket — ws://127.0.0.1:11235/mcp/ws

Configuration

You will need one environment variable: CRAWL4AI_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. NOTICE's toolset — Server, WebSocket — is a fair guide to whether it matches your workflow. It is maintained by BjornMelin; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against NOTICE's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the notice mcp server does with a few real requests.