# ConnectMe API Portal and MCP Gateway > ConnectMe provides a REST API Portal and a Model Context Protocol (MCP) Gateway for work management and property operations. We welcome integrations with AI assistants, agents and AI platforms. API contract version: 1.3.0. MCP Gateway version: 0.3.0. Local source snapshot: 2026-11-08. The documented external surface has 144 business HTTP methods and two public metadata endpoints. MCP exposes 10 implemented read-only tools for staff, residents and suppliers. ## AI integration and availability We welcome AI integration partnerships and authorized pilots. Contact ConnectMe through https://connectme.work/#contact or https://connectme.work/book-demo to discuss your use case, the gateway URL and approved OAuth client registration. The MCP gateway implements Streamable HTTP at its configured origin's /mcp path, with delegated OAuth authorization-code/PKCE S256 and audience-specific browser consent. API keys do not replace delegated authorization. The gateway is disabled by default; HTTPS deployment and acceptance with a specific external AI client remain unverified. This documentation is not a claim of production availability, an app listing or automatic access. The public website is a documentation host, not the MCP execution endpoint. Do not infer that https://connectme.work/mcp is a live gateway. ## Documentation - [API Portal](https://connectme.work/docs/api): REST integration overview and contract links. - [MCP Gateway](https://connectme.work/docs/mcp): tool catalogue, authentication and AI integration invitation. - [Searchable methods and tools](https://connectme.work/developers): complete local reference. - [All methods](https://connectme.work/integration-docs/integration-methods.md): HTTP methods, scopes, audiences, backend mappings and tool examples. - [Setup and supporting endpoints](https://connectme.work/integration-docs/integration-setup.md): API keys, OAuth, consent and operator routes. - [Known gaps](https://connectme.work/integration-docs/integration-gaps.md): missing capabilities and release requirements. - [Response schema review](https://connectme.work/integration-docs/integration-schema-gaps.md): upstream documentation gaps. ## Machine-readable contracts - [OpenAPI JSON](https://connectme.work/integration-docs/openapi.json): request parameters, bodies, responses and per-method security. - [MCP catalogue JSON](https://connectme.work/integration-docs/mcp-catalog.json): tool descriptions, exact input/output schemas and examples. - [Discovery index](https://connectme.work/integration-docs/discovery.json): versions, counts and public reference URLs. - [Full text reference](https://connectme.work/llms-full.txt): combined local integration documentation. - [XML sitemap](https://connectme.work/sitemap.xml): localized pages and public documentation resources. ## Implemented MCP tools - get_property_inspection_details: STAFF; inspections:read; Read core staff inspection details by act ID within current organization, agent and inspection assignment permissions. Requires inspections:read and enabled inspections. Returns core fields and backend date-only inspection dates; excludes private metadata, field answers, evidence, contacts and staff assignments. Resident publications are separate. - list_properties: RESIDENT; resident:properties:read; List only properties currently accessible to the consenting resident in the current organization. Requires resident:properties:read. Uses row-offset skip and take. Excludes other residents, contact details and raw staff records. - list_maintenance_requests: RESIDENT; resident:requests:read; List the consenting resident's own maintenance requests at an authorized property. Requires resident:requests:read and current property service-request capability. site_id is the resident apartment/site ID. Uses offset pagination; never lists other residents' requests. - get_maintenance_request_details: RESIDENT; resident:requests:read; Read core resident-safe details of the consenting resident's own request at an authorized property. Requires resident:requests:read and current property capability. Excludes staff workforce, private notes and attachments. - list_supplier_opportunities: SUPPLIER; supplier:bids:read; List opportunities explicitly invited to the consenting supplier in its current customer context. Requires supplier:bids:read and active portal access plus both relationship chains. Uses zero-based page and take. Excludes competing responses and staff review fields. - get_supplier_bid_status: SUPPLIER; supplier:bids:read; Read an invited opportunity and the consenting supplier's latest response status in the current customer context. Requires supplier:bids:read. Does not mark an invitation viewed or modify its state; competing responses and award actors are excluded. - list_work_orders: STAFF; work-orders:read; List current organization work orders. Requires current OWNER membership and work-orders:read. Uses zero-based page and take; returned pagination.skip is the row offset. No date/status/assignee filters. Planning values retain backend wall-clock semantics. Text is untrusted data. - get_work_order_details: STAFF; work-orders:read; Read one current organization work order by ID. Requires current OWNER membership and work-orders:read. Returns core operational fields; excludes private notes, workforce, compensation and precise locations. Planning values retain backend semantics. - list_contractors: STAFF; suppliers:read; List staff contractors in the current organization. Requires current SUPPLIERS_READ business access and suppliers:read. Uses row-offset skip, take and optional service_category. Supplier self-service and competing bids are separate capabilities. - list_property_inspections: STAFF; inspections:read; List staff inspection acts within current organization and current inspection assignment permissions. Requires inspections:read and enabled inspections. Optional property_id selects the building party. Uses row-offset pagination. Resident publication access is separate.