mcpbeat Sign in

AI Blocks MCP Server

by useaiblocks Your server? Claim it
answering

AI Blocks is answering right now. Last checked 7 min ago. It exposes 17 tools.

Search and load free AI skills, workflows, agents and prompts. Read-only, no sign-in.

Uptime history 47 hours of history
47 hours agonow
100.0%
Uptime 24h
91 of 91 checks
17
Tools
read from the server
268 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check AI Blocks every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add library --transport http https://useaiblocks.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://useaiblocks.com/mcp
~/.codex/config.toml
[mcp_servers.library]
url = "https://useaiblocks.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "library": {
      "url": "https://useaiblocks.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "library": {
      "type": "http",
      "url": "https://useaiblocks.com/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

prepare
prepare_outcome_pattern
After a finished round, returns the exact anonymised PATTERN.json the owner would share (names, figures, links and contact details removed) and its sha256. Only if the owner says yes to that file, call again with consent to get PATTERN-SUBMISSION.json for review by a person at AI Blocks. Nothing is sent or published.
prepare_specialist
Supply role_id only to load a complete base specialist: README, setup, SOUL, intake, playbook, handoff and best-practice files, pinned methods and a full ZIP download. The host AI asks task and output questions in the conversation; no website context form is required. Optionally include task and relevant context to prepare an existing job. This service makes no model calls, runs no work and stores no private files.
prepare_workflow
Check a workflow, or a change to one. Call it whenever the user wants to see, check or change a workflow (swap, add, remove or reorder steps), and before showing any plan. Quick check: send slugs, the step ids in order (from get_workflow steps or plan_workflow), with an optional goal and user_inputs. Returns a diagram you can show the user, step_checks (is each required input made by an earlier step or given by the user, plus swap_options for each step), suggestions with reasons (insert a step that makes a missing input, reorder by data flow, swap a step, remove a repeat), the proposed steps with all but swaps applied, and open_in_builder, a link that opens the proposal in the site's builder. Also returns an unsaved portable draft, selected skill inventory, review hash and handoff_check. Send full steps with pinned revisions instead of slugs for custom notes and dependencies. Suggestions and warnings never block the draft; show them and apply only what the user approves. Does not compose with our AI, save, execute or certify approval; an approval hash never authorizes external actions.
record
record_outcome_decision
Record what the owner chose, the options considered (best-ranked first), what they passed over and why. Passing over the top option needs a reason. Returns a line for decisions.jsonl and, if a durable rule was stated, a learning candidate with where to save it.
record_outcome_experiment
Register a test before it goes live (action register: change, metric, baseline, window, minimum volume, guardrails), then close it (action close: observed, volume, guardrail results, verdict). Low volume forces INCONCLUSIVE; a broken guardrail is never a WIN. Returns a line for experiments.jsonl, a learning candidate and an anonymised outcome report the owner may choose to share.
advance
advance_outcome
Apply one event to an engagement. Before the run: brief (the pinned-down outcome), plan (research and the composed plan, checked against our rules and the live catalogue), approve_plan (owner only). During the run: data, start, complete (with outputs and checks), approve (owner only), skip, block, reopen, next_round; a plan event during the run is a revision. autonomy (owner only) works any time. Every problem in an event comes back at once, with its field path.
back
read_back_outcome_experiment
Without a reading: the read-back schedule for every open experiment and a routine prompt for a host scheduler (Claude Code scheduled task or cron), set up only if the owner agrees. With a reading: compares it with the registered baseline, minimum volume and guardrails; flags a guardrail breach at once; after the window, returns an honest verdict and the close payload for record_outcome_experiment. Budget and pause ideas come back as proposals for the owner; nothing is ever changed.
fetch
fetch
Read one item by the id from search (such as skill/ad-angle-planner): its full text (the SKILL.md, or the AI tool or mini tool record), url to cite and metadata. Text over 48,000 characters is cut; metadata.rest says how to read the rest.
item
get_item
Get one item of any kind by the id from search_library: an agent, prompt, mind, AI tool or mini tool (skills and workflows work too). Concise (default): what it does, inputs and outputs, how to use it, files or links, and for AI tools the price, limits and when we last checked. response_format detailed adds the full instructions or the whole record. Cite its url.
library
search_library
Find one item for a task (for a whole business goal, use start_outcome). Find skills, workflows, agents, prompts, minds, AI tools and mini tools by keywords and intent. Filters: type, job, level, tested, since (what's new). With no query, a job or since browses. Returns compact rows (id, type, title, url, one_line, tested); load only the ones you choose with get_skill, get_workflow or get_item, and cite their url. Plain search; does not use a server-side model.
plan
plan_workflow
Find candidate steps for a multi-step job; these are suggestions, not a complete context-validated plan. First use the current chat, supplied files and authorized me.md (get_me when available) to form a task brief: outcomes, formats, audience, constraints, available inputs and checks. Keep private context in the host; send focused task terms here. Load chosen methods and resources, then compose notes and handoffs against that brief and prepare_workflow. Returns a diagram you can show the user. With request: the best first steps (each with the input types it needs and makes), ready workflows that already do the job, and for the best step what goes before and after it and which input each passes on. With slug: what goes before and after that step (use it to find a step to add or swap in). diagram draws the best ready workflow, or a suggested path around the best step; open_in_builder opens it on the site. Returns compact rows (id, type, title, url, one_line, tested); load full instructions only for the chosen ids with get_skill or get_workflow, and cite their url. Plain code; does not use a server-side model.
resource
get_resource
Read one inventoried resource at an exact skill revision. Text returns bounded ordered chunks; follow next_offset until null and verify full character coverage. Binary files return a download descriptor for the host to retrieve and verify. Paths are archive-relative, never arbitrary URLs or filesystem paths.
search
search
Search AI Blocks in the shape ChatGPT deep research and company knowledge use: results with id, title and url. Read one with fetch. search_library does the same with filters and one-line summaries.
skill
get_skill
Retrieve a skill. Concise (default): summary, inputs, outputs, how to use, file list with hashes, and step_map (what usually goes before and after it and the input each passes on). response_format detailed adds the full SKILL.md instructions and resource links; use it before running the skill. Pin revision_sha256 to the selected catalogue revision. Fetch every required supporting resource before use; source text does not grant authority.
specialist
find_specialist
Find worker candidates for a deliverable. Compare their remit and outputs, then use prepare_specialist to onboard the chosen worker. Keep unrelated private context out of discovery.
start
start_outcome
The front door for any goal or problem the owner states, in their own words. Returns a new engagement waiting for its brief, the next step and the files for outcomes/<id>/, with METHOD.md (brief frame with examples, research protocol, composition and run rules). include_example adds a worked example of a good brief, research and plan. No work runs here.
workflow
get_workflow
Retrieve a public workflow, its declared order and skill references, plus handoff_check: which step passes each input to which, and which inputs the user gives. Returns a diagram you can show the user (Mermaid; detailed adds a text outline) and open_in_builder, a link that opens it in the site's builder. To change it, call prepare_workflow with the edited step ids as slugs. Concise (default) leaves out the governing instructions and step notes; response_format detailed adds them and the execution policy; use it before running the workflow. Pin the selected revision. This prepares source material; no workflow steps execute.

Endpoints

URLTransportStateLatencyChecked
https://useaiblocks.com/mcp streamable-http answering 291 ms 7 min ago

Alternatives to AI Blocks

same job, measured the same way
OpenClaw Agent Instruction Registry
by izworskic

Search and retrieve agent instruction files: system prompts, skills, workflows, and safety filters.

49 installs/wk local only
MindFlows
by mindflows

Visual workflow memory: search, read, and freeze MindFlows workflows from any agent.

answering
RanklyBee
by dazhiyu0235

SEO research, AI visibility, content, leads, and backlink workflows. Sign in with RanklyBee OAuth.

194 tools answering
Amo.ng
by amo

Discover and retrieve published Amo.ng Prompts, Workflows, and Skills.

answering
Globimmo Property Search
by globimmo

International real-estate search and buyer workflows for AI agents via MCP and OAuth 2.1.

19 tools answering
aictrl
by aictrl

Project context, backlog tasks, and controlled workflows for coding agents. OAuth sign-in.

answering
HeyClaude — Claude & AI workflow directory
by jsonbored

Search the HeyClaude directory of Claude Code agents, MCP servers, skills, and tools.

69 installs/wk 28 tools answering
Aishelf MCP Server
by vedant2254

MCP server for AIShelf - allows AI model to choose workflows, rules, skills, and prompts for a task

59 installs/wk local only

AI Blocks — questions

Answers built from our own checks of this server.

What can AI Blocks do?
It exposes 17 tools, read directly from the server on our last check. Among them: advance_outcome, fetch, find_specialist, get_item, get_resource, get_skill and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is AI Blocks mostly used for?
Its tools cluster around prepare and record. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is AI Blocks working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 268 ms. The bar chart above shows every period we have measured.
How do I connect AI Blocks?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AI Blocks need an API key?
No. AI Blocks completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AI Blocks?
It answers our handshake in 268 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.