generated: '2026-07-26'
method: searched
status: published
maturity: alpha
source: https://foundations-documentation.reapit.cloud/api/mcp-alpha
description: >-
  The Reapit Foundations MCP server is a real, hosted, first-party Model Context
  Protocol server that exposes the agency CRM platform to agents over a single
  Streamable HTTP endpoint. It is in alpha and behind an early-access form, and
  an anonymous tools/list POST returns 401 {"error":"No authorization header
  provided"} — so the tool names and domains below are the ones Reapit itself
  publishes in the documentation, not a live introspection. Input schemas are
  NOT published and require an authenticated tools/list call; see
  reapit-tool-crosswalk.yml for how each tool binds to a real GraphQL operation
  whose arguments are introspectable anonymously.
server:
  name: foundations
  transport: streamable-http
  url: https://foundations-mcp.iaas.reapit.cloud/mcp
  docs: https://foundations-documentation.reapit.cloud/api/mcp-alpha
  early_access: form
  early_access_note: >-
    Registration is by HubSpot form linked from the MCP alpha documentation page.
authentication:
  scheme: bearer
  issuer: https://connect.reapit.cloud/
  token: Reapit Connect JWT (access token)
  required_scope: agencyCloud/mcp.access
  required_scope_note: A token without this scope is rejected with 403.
  tenant_header:
    name: reapit-customer
    required_for: machine-to-machine (client-credentials) clients only
    note: >-
      User-context tokens carry the customer code themselves, so the header is
      not needed. Sandbox tenant id is SBOX.
  optional_headers:
  - name: x-timezone
    default: UTC
    example: Europe/London
    note: converts date-times in the formatted text stream output
live_probe:
  method: 'POST tools/list (jsonrpc 2.0), Accept: application/json, text/event-stream'
  status: 401
  body: '{"error":"No authorization header provided"}'
  probed: '2026-07-26'
  well_known:
  - path: /.well-known/oauth-protected-resource
    status: 401
  - path: /.well-known/oauth-authorization-server
    status: 401
  note: >-
    Unusually, even the RFC 9728 protected-resource metadata is auth-gated, so
    an MCP client cannot discover the authorization server anonymously — it must
    be told to use Reapit Connect out of band.
errors:
- status: 400
  meaning: Bad request — e.g. a client-credentials token without the reapit-customer header.
- status: 401
  meaning: Unauthorized — missing, expired, or invalid token.
- status: 403
  meaning: Forbidden — valid token, but lacking the agencyCloud/mcp.access scope.
- status: 502
  meaning: Upstream verification failure (identity provider unreachable).
behaviour:
  embedded_resources: >-
    The server applies Foundations "embeds" automatically — an appointment comes
    back with its negotiators, office and property attached rather than just
    their ids. Reapit documents this as convenient but subject to change, so
    agents must not assume a fixed set of embedded fields.
  stability: >-
    Reapit states parameters, tools, resources, prompts and responses are likely
    to change, and that List Tools is the authoritative current set per tenant.
client_config:
  mcpServers:
    foundations:
      type: streamable-http
      url: https://foundations-mcp.iaas.reapit.cloud/mcp
      headers:
        Authorization: Bearer <your-jwt>
        reapit-customer: <your-tenant-id>
tool_count: 43
tools:
- name: appointments_search
  domain: appointments
  description: Search appointments in the diary.
- name: appointments_get_by_id
  domain: appointments
  description: Retrieve a single appointment.
- name: appointments_create
  domain: appointments
  description: Create an appointment.
- name: appointments_update
  domain: appointments
  description: Update an appointment.
- name: appointments_get_types
  domain: appointments
  description: List appointment types (configuration lookup).
- name: appointments_get_followup_responses
  domain: appointments
  description: List appointment follow-up responses (configuration lookup).
- name: appointments_list_open_house_attendees
  domain: appointments
  description: List attendees of an open-house appointment.
- name: appointments_create_open_house_attendee
  domain: appointments
  description: Add an attendee to an open-house appointment.
- name: appointments_update_open_house_attendee
  domain: appointments
  description: Update an open-house attendee.
- name: appointments_delete_open_house_attendee
  domain: appointments
  description: Remove an open-house attendee.
- name: properties_search
  domain: properties
  description: Search properties.
- name: properties_get_by_id
  domain: properties
  description: Retrieve a single property.
- name: get_directions
  domain: properties
  description: Get driving directions between locations.
- name: properties_appraisals_list
  domain: properties
  description: List property appraisals.
- name: properties_appraisals_get
  domain: properties
  description: Retrieve a property appraisal.
- name: properties_appraisals_create
  domain: properties
  description: Create a property appraisal.
- name: properties_appraisals_update
  domain: properties
  description: Update a property appraisal.
- name: properties_key_movements_list
  domain: properties
  description: List key movements for a property key.
- name: properties_key_movements_create
  domain: properties
  description: Record a key check-out.
- name: properties_key_movements_check_in
  domain: properties
  description: Record a key check-in.
- name: get_departments
  domain: configuration
  description: List departments.
- name: get_property_attribute_options
  domain: configuration
  description: List the valid property attribute options.
- name: companies_get_types
  domain: configuration
  description: List company types.
- name: contacts_search
  domain: contacts
  description: Search contacts.
- name: contacts_get_by_id
  domain: contacts
  description: Retrieve a single contact.
- name: contacts_create
  domain: contacts
  description: Create a contact.
- name: contacts_update
  domain: contacts
  description: Update a contact.
- name: applicants_search
  domain: applicants
  description: Search applicants (prospective buyers/renters).
- name: applicants_create
  domain: applicants
  description: Create an applicant.
- name: applicants_update
  domain: applicants
  description: Update an applicant.
- name: companies_search
  domain: companies
  description: Search companies.
- name: offices_search
  domain: offices
  description: Search offices.
- name: offices_get_by_id
  domain: offices
  description: Retrieve a single office.
- name: negotiators_search
  domain: negotiators
  description: Search negotiators (agency staff).
- name: negotiators_get_by_id
  domain: negotiators
  description: Retrieve a single negotiator.
- name: areas_search
  domain: areas
  description: Search areas (agent-defined geographies).
- name: offers_search
  domain: offers
  description: Search offers.
- name: landlords_search
  domain: landlords
  description: Search landlords.
- name: landlords_get_by_id
  domain: landlords
  description: Retrieve a single landlord.
- name: vendors_search
  domain: vendors
  description: Search vendors.
- name: vendors_get_by_id
  domain: vendors
  description: Retrieve a single vendor.
- name: tenancies_search
  domain: tenancies
  description: Search tenancies.
- name: tenancies_get_by_id
  domain: tenancies
  description: Retrieve a single tenancy.
related_mcp_servers:
- name: Reapit Elements design system / component library MCP
  source: https://foundations-documentation.reapit.cloud/app-development/elements
  note: >-
    The Elements documentation states the Design System (design.reapit.cloud)
    and component library (elements.reapit.cloud) docs are both available via
    MCP for coding agents. Endpoint URLs are given in the Elements Getting
    Started guide rather than the Foundations docs, so they are recorded here as
    a pointer, not harvested.