RESO Cloud MCP Server

aid: reso:reso-cloud-mcp
name: RESO Cloud MCP Server
description: 'The RESO Cloud MCP Server is the one production API endpoint RESO itself operates. It speaks
  the Model Context Protocol over Streamable HTTP at https://services.reso.org/mcp and exposes the RESO
  toolchain to AI agents - authenticate, query, metadata, create, update, delete and parse-filter - so
  an agent can work against any RESO-certified OData server without knowing OData syntax. It is a broker,
  not a data source: every tool call takes a target server URL and that server''s credentials, and RESO
  stores no listing data behind it. Access is beta and gated on an API key issued by RESO on request to
  dev@reso.org, available to RESO members and conference attendees; an anonymous tools/list returns HTTP
  401 with a JSON-RPC error pointing at that address. The same tool interfaces are available offline via
  the local stdio server (@reso-standards/reso-mcp-server), which adds the validate, run-compliance and
  metadata-report certification tools.'
humanURL: https://tools.reso.org/packages/reso-mcp-server
baseURL: https://services.reso.org/mcp
tags:
- MCP
- AI Agents
- OData
- Certification
- Tooling
properties:
- type: MCPServer
  url: mcp/reso-mcp.yml
  name: RESO MCP server manifest (hosted cloud server + local stdio server)
- type: ToolCrosswalk
  url: mcp/reso-tool-crosswalk.yml
  name: MCP tool to OData request-form crosswalk
- type: Documentation
  url: https://github.com/RESOStandards/reso-tools/blob/main/reso-mcp-server/doc/GUIDE.md
  name: RESO MCP Server User Guide
- type: Documentation
  url: https://github.com/RESOStandards/reso-tools/blob/main/reso-mcp-server/README.md
  name: RESO MCP Server README
- type: Authentication
  url: authentication/reso-authentication.yml
  name: API-key bearer auth on the cloud server; OAuth2 pass-through to target servers
- type: SourceCode
  url: https://github.com/RESOStandards/reso-tools/tree/main/reso-mcp-server