# RetailHardHat MCP developer documentation

RetailHardHat is an inbound, tenant-bound MCP server, not a general-purpose proxy or an outbound MCP client. An active organization owner/admin issues each connection. Platform-superadmin privileges are never delegated.

Organization administrators use Settings → MCP for client setup, connections,
approvals, tools, security and activity. Publisher checklists, domain verification
and provider-directory submission requirements belong to Platform Admin → MCP
Administration → Publishing (`/platform-admin/mcp`). Its API, `/api/platform/mcp/provider-readiness`,
requires platform authorization. Tenant setup exposes only connection URLs through
`/api/mcp-admin/connection-setup`, not publishing status.

Organization, per-user and per-connection usage ceilings are managed in Platform
Admin → MCP Administration → Usage budgets. Tenant admins may tighten individual
connections but cannot change their organization's platform allocations.

## Start here

- [Quickstart and runnable client](quickstart.md)
- [Protocol, tools and response reference](reference.md)
- [Authentication and OAuth](authentication.md)
- [Security policies and management API](security.md)
- [Adding tools and native views](extending.md)
- [Testing and release checks](testing.md)
- [Troubleshooting](troubleshooting.md)
- [Provider distribution](../mcp-providers/README.md)
- [Native dashboards and discovery](../mcp-providers/native-views-and-discovery.md)
- [Provider review checklist](../mcp-providers/review-checklist.md)
- [Operational connector guide](../mcp.md)

## Public reference

The same guides are served at `/api/mcp-public/docs`. Each guide has an HTML page and a `.md` download. The read-only endpoints below contain definitions, not organization records:

| Endpoint | Contents |
| --- | --- |
| `/api/mcp-public/catalogue` | Business and outcome tool definitions |
| `/api/mcp-public/reference` | Tool catalogue including approval controls, modules, protocol resources and policy defaults |
| `/api/mcp-public/security-schema` | JSON Schemas generated from the enforced organization and connection policy validators |

The public catalogue is the universe of implemented tools, **not** a permission grant. Authenticated `tools/list` is authoritative for the connected client's advertised tools; authorization and sharing checks also run during execution. A listed tool can still be denied for a record, document, quota or policy restriction.

## Boundaries

One MCP server supports multiple providers. Shared MCP Apps views use the MCP Apps SDK, with optional OpenAI host enhancements. Model inference SDKs are not required to expose this server. Compatible non-UI clients receive text and structured data. Do not assume every provider/account supports widgets or directory submission.

Local protocol tests, generated submission packages and tool-selection benchmarks do not establish provider acceptance, real-account behavior or recommendation ranking. Publication and provider review are separate operator actions.

Never commit credentials, real customer data, consent captures or private tool results into examples or documentation. Public documentation must remain safe to read without signing in.