{
  "anchor_concepts": [
    {
      "name": "MCP for tools",
      "summary": "MCP lets an agent discover and call context tools inside its working environment."
    },
    {
      "name": "REST for services",
      "summary": "REST is better for backend integrations, scheduled jobs, and controlled application flows."
    },
    {
      "name": "Same context graph",
      "summary": "Both can expose the same sources, streams, tags, records, and manifests behind Synorb."
    },
    {
      "name": "HC reference role",
      "summary": "Hanging Context is the public reference layer, not the delivery endpoint."
    }
  ],
  "boundary": "public_reference_page_not_retrieval_api",
  "canonical_url": "https://hangingcontext.com/definitions/mcp-vs-rest-for-agent-context/",
  "generated_at": "2026-05-20T12:17:55+00:00",
  "html_url": "https://hangingcontext.com/definitions/mcp-vs-rest-for-agent-context/",
  "json_url": "https://hangingcontext.com/data/definitions/mcp-vs-rest-for-agent-context.json",
  "page_type": "definition_citation_page",
  "related_hc_surfaces": [
    "/sources/",
    "/streams/",
    "/tags/",
    "/mcp/"
  ],
  "schema_version": 1,
  "summary": "MCP and REST are delivery patterns for agent context: MCP fits tool-using agents, while REST fits application services and backend workflows.",
  "target_queries": [
    "MCP vs REST for agent context",
    "MCP data source for agents",
    "agent context API"
  ],
  "term": "MCP vs REST for agent context"
}