Skip to main content
RCP is an open standard, and we want the ecosystem to signal compatibility clearly. These assets and guidelines help you do that consistently. The name and these guidelines are free to use to indicate that your project speaks RCP.

​
The name

  • The protocol is the Retrieval Context Protocol, abbreviated RCP.
  • A specific wire version is written RCP/1 (the 1 is the negotiated protocolVersion).
  • Prefer “speaks RCP”, “an RCP server”, or “RCP-compatible” over possessive or product-like phrasings.
One-liner you can reuse: “RCP is one open, versioned JSON-RPC protocol so any RAG engine can expose embed, rerank, retrieve, graph, and index — and any client can consume it uniformly.”
The mark ships in two variants tuned for light and dark backgrounds.
RCP logo

Light background

/logo/light.svg — dark mark for use on light surfaces.

Dark background

/logo/dark.svg — light mark for use on dark surfaces.

​
Colors

The palette is built around a single emerald primary with a lighter and darker step for hover and dark-mode states. Type is set in Lora for headings and Inter for body — but any clean serif/sans pairing preserves the feel.

​
Using the mark

Please do

Use the logo to show your project is RCP-compatible. Keep clear space around it. Use the variant that matches your background.

Please don't

Recolor or distort the mark, imply endorsement of a closed product, or use the name in a way that suggests RCP is your project rather than an open standard.
Building something on RCP? Open an issue or PR and we are glad to link real-world engines, clients, and SDKs from the docs.