foundations
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.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport streamable-http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
appointments_search— Search appointments in the diary.appointments_get_by_id— Retrieve a single appointment.appointments_create— Create an appointment.appointments_update— Update an appointment.appointments_get_types— List appointment types (configuration lookup).appointments_get_followup_responses— List appointment follow-up responses (configuration lookup).appointments_list_open_house_attendees— List attendees of an open-house appointment.appointments_create_open_house_attendee— Add an attendee to an open-house appointment.appointments_update_open_house_attendee— Update an open-house attendee.appointments_delete_open_house_attendee— Remove an open-house attendee.properties_search— Search properties.properties_get_by_id— Retrieve a single property.get_directions— Get driving directions between locations.properties_appraisals_list— List property appraisals.properties_appraisals_get— Retrieve a property appraisal.properties_appraisals_create— Create a property appraisal.properties_appraisals_update— Update a property appraisal.properties_key_movements_list— List key movements for a property key.properties_key_movements_create— Record a key check-out.properties_key_movements_check_in— Record a key check-in.get_departments— List departments.get_property_attribute_options— List the valid property attribute options.companies_get_types— List company types.contacts_search— Search contacts.contacts_get_by_id— Retrieve a single contact.contacts_create— Create a contact.contacts_update— Update a contact.applicants_search— Search applicants (prospective buyers/renters).applicants_create— Create an applicant.applicants_update— Update an applicant.companies_search— Search companies.offices_search— Search offices.offices_get_by_id— Retrieve a single office.negotiators_search— Search negotiators (agency staff).negotiators_get_by_id— Retrieve a single negotiator.areas_search— Search areas (agent-defined geographies).offers_search— Search offers.landlords_search— Search landlords.landlords_get_by_id— Retrieve a single landlord.vendors_search— Search vendors.vendors_get_by_id— Retrieve a single vendor.tenancies_search— Search tenancies.tenancies_get_by_id— Retrieve a single tenancy.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.