Point your client at the server
The MCP endpoint is https://getfoyer.app/mcp. Any MCP-capable client can register itself — nothing needs to be set up on our side first.
claude mcp add --transport http foyer https://getfoyer.app/mcpThe first call returns 401 with a WWW-Authenticate header naming the protected-resource metadata document. An OAuth-capable client follows it, registers itself, and runs an authorization-code flow with PKCE. Your browser opens, the operator picks full or read-only access, and the client holds a token afterwards.
Give your agent the documentation
This portal publishes itself in machine-readable form. https://developer.getfoyer.app/llms.txt is a short index; https://developer.getfoyer.app/llms-full.txt is every guide plus the whole tool catalogue in one file, so an agent can read the entire surface in a single fetch instead of crawling twelve pages.
curl https://developer.getfoyer.app/llms-full.txtKnow what you are calling
Ask the server what it has: an MCP tools/list call returns the authoritative name, description and schema for every tool your credential can see — which is fewer than the full registry if the key is scoped. Start with read-only tools while you find your way; they cannot change anything a hotel depends on.
Without OAuth
For your own scripts an API key from Settings → API keys works against the same endpoint, no browser round-trip. Send it as a bearer token; the key's role and module scope are enforced on every tool call.