Blue Reacher
Build with AI6 / 54

Build with AI

Every way to hand Blue Reacher to an AI: the hosted MCP server for agents that act, and machine-readable docs for assistants that write your integration.

There are two jobs an AI can do with Blue Reacher, and each has its own entry point.

Connect an agent in one command

The MCP server is hosted, so there is nothing to install or keep running. Try it first with the public sandbox key:

claude mcp add --transport http bluereacher https://api.bluereacher.com/v1/mcp \
  --header "Authorization: Bearer brk_test_Dc815ar0WQChF5odYSeB8k2ovmVf1zG2"

Nothing real is sent on that key. Swap in your live key when you are ready. Cursor, Claude Desktop and generic client configs, the full tool list and the safety rules are on the MCP server page.

Docs for your assistant

Point a coding assistant at these and it works from the real API instead of guessing.

WhatURLUse it for
Docs indexhttps://docs.bluereacher.com/llms.txtA map of every page, small enough for any context window
Full docshttps://docs.bluereacher.com/llms-full.txtEvery page in one text file
Any single pageAdd .md to its URL, for example https://docs.bluereacher.com/docs/guides/quickstart.mdJust the page you are working on
OpenAPI spechttps://docs.bluereacher.com/openapi.jsonTypes, request shapes and client generation

Requesting any /docs page with Accept: text/markdown also returns the markdown version.

Every page on this site has a Copy Markdown button under its title, and the menu next to it opens the page directly in ChatGPT, Claude and other assistants.

A prompt that works

Paste this into your assistant with the files above attached or linked:

Using the Blue Reacher API docs at https://docs.bluereacher.com/llms-full.txt,
write a function that sends an iMessage with an Idempotency-Key, and a webhook
handler that verifies X-BlueReacher-Signature before parsing. Test it against
the public sandbox key brk_test_Dc815ar0WQChF5odYSeB8k2ovmVf1zG2.

Keep agents safe

  • Build on a test key first. The simulator answers every tool with nothing real sent.
  • Give the agent its own key, so one revoke stops it without touching your production integration.
  • Keep bulk sends human-approved. Drafting and research are safe to automate; approving outbound to real people is a product decision.
  • Pacing and opt-outs are enforced underneath, so an over-eager agent queues rather than burns a line, and it cannot message a contact who opted out.

On this page