Hosted MCP
Your always-on Powerloom MCP endpoint. Put the URL + a PAT into Codex CLI, Gemini CLI / Antigravity, Claude Code, or another MCP client and every tool in your org's catalog becomes callable ? no install, no proxy, rate-limited + audited at the control plane.
Loading…
Subdomain routing ? the proxy UUID is separate from your internal user id so it can rotate without breaking database FKs.
…
Mint a PAT at /settings/access-tokens and export it as POWERLOOM_PAT before launching your MCP client (or hardcode it if you know what you're doing). The same endpoint works with Codex CLI, Gemini CLI / Antigravity, Claude Code, or another compatible MCP client.
By default every skill in your org catalog is callable via the dispatcher: the MCP client calls powerloom_list_skills, picks one, then invokes it with powerloom_invoke_skill. Promoting a skill here makes it appear as a top-level tool in clients with a first-class tool picker ? skip the list-before-invoke round-trip for frequently-used skills. No limit on count, but large allowlists make the tool list noisy; pick 5?15.
Your org has no tool_definition skills yet.
Create one at /skills to see it here. Archive-kind skills don't appear ? they're not MCP-callable.
Every tool invocation via this endpoint writes paired rows to the compliance audit log + work-chain event stream. The server records an args_hash (SHA-256 of sorted-JSON-encoded args) rather than raw args ? tool inputs can contain PII or customer data.
Inspect at /audit ? filter by resource_kind=hosted_mcp_tool.