Hemlo · Agent Skills

Let your AI agent do the broker work in Hemlo

Skills and an MCP server for Hemlo, the assistant for Swedish real estate brokers. Claude, ChatGPT, Cursor or Codex can run deals, capture seller meetings, write and style listing drafts and keep your Stilprofil up to date — as you, with your permissions.

Install the skills

npx skills add https://skills.staging.hemlo.ai

Works with any agent that follows the Agent Skills spec (Claude Code, Codex, Cursor, …). The catalog is published at /.well-known/agent-skills/index.json.

Skills

hemlo

Work as a Swedish real estate broker (mäklare) in Hemlo — deals (affärer), seller meetings, intake capture, Trygghetskoll checks, listing drafts (annonsutkast), style profiles (Stilprofil) and approvals. Use when the user mentions Hemlo, their deals, listings, sellers, meetings or the Hemlo API/MCP. Routes to hemlo-mcp, hemlo-api and hemlo-keys.

npx skills add https://skills.staging.hemlo.ai --skill hemlo

hemlo-mcp

Connect to and use the Hemlo MCP server (Streamable HTTP, bearer API key) so an agent such as Claude, ChatGPT, Cursor or Codex can do a broker's work in Hemlo — deals, meetings, capture, listing drafts, Stilprofil and approvals. Use when setting up the Hemlo MCP connection or choosing which Hemlo tool to call.

npx skills add https://skills.staging.hemlo.ai --skill hemlo-mcp

hemlo-api

Call the Hemlo REST API (/api/v1) for broker work — deals, meetings and capture, tasks, documents, Trygghetskoll checks, listing drafts, discrepancies, style profiles with sold-listing links, and approvals. Use for scripts, integrations or agents without MCP support, or when you need exact request/response shapes.

npx skills add https://skills.staging.hemlo.ai --skill hemlo-api

hemlo-keys

Create, scope, store, rotate and revoke Hemlo API keys (hsk_u_ personal, hsk_o_ organization) for agents and integrations. Use when a Hemlo call returns 401/forbidden, when setting up the Hemlo MCP server or API for the first time, or when the user asks about Hemlo access, scopes or keys.

npx skills add https://skills.staging.hemlo.ai --skill hemlo-keys

Connect the MCP server

https://api.staging.hemlo.ai/api/mcp — Streamable HTTP, 46 tools generated from the Hemlo API contract. Every tool runs as your broker account with your roles and key scopes, and is logged with channel mcp.

claude mcp add --transport http hemlo https://api.staging.hemlo.ai/api/mcp \
  --header "Authorization: Bearer $HEMLO_API_KEY"

{
  "mcpServers": {
    "hemlo": {
      "url": "https://api.staging.hemlo.ai/api/mcp",
      "headers": { "Authorization": "Bearer ${HEMLO_API_KEY}" }
    }
  }
}

Clients need to send an Authorization header; OAuth sign-in (needed by some ChatGPT connectors) is not supported yet.

Authentication

Key	Acts as	Scopes
`hsk_u_…`	You, the signed-in broker	`me:read` · `deals:read` · `deals:write`
`hsk_o_…`	The firm's integration account	same

Create a key in Hemlo Admin → API keys & agents. An agent that should do your work needs all three scopes. Keep the key in your client's secret store, never in chat.

Smoke test

curl -s https://api.staging.hemlo.ai/api/v1/me \
  -H "Authorization: Bearer $HEMLO_API_KEY" \
  -H "x-hemlo-channel: mcp"

Then ask your agent: “What do I have today in Hemlo?” — it calls get_me and get_broker_today.