Skip to content
Artifactum Content Objects · MCP
Open vault

Auth

Hosted identity vs your OAuth

Artifactum is an MCP resource server. Sign-in is an identity-provider job. Hosted Estes Artifactum is tested with Auth0 under the hood — Auth0 is not the product, and customers are not asked to “log into Auth0” as if it were the vault.

Two deployments

Mode Who owns identity What you connect to
Hosted (Estes) Estes operates the identity provider (tested with Auth0) and issues you an account / Bearer. https://mcp.artifactum.ai/
Dedicated / single-tenant You bring your own OAuth / IdP. Artifactum validates your tokens (issuer, audience, JWKS). Your MCP host, in your account

Roadmap: single-tenant hosted now; multi-tenant SaaS later. This documentation is story and getting started, not a paywall or a price list.

Hosted: how you actually sign in

  • Human vault UI — app.artifactum.ai sends you through the hosted login screen, then uses a public PKCE client. There is no client secret in the browser.
  • Cursor / CLI — long-lived Bearer in the process environment. That is the supported daily path. See Cursor. Do not paste tokens into git, issues, or chat.
  • Grok Web — connector URL is the MCP host; the hosted login screen completes in the browser.
  • Grok iOS — same hosted connector path as Grok Web. Not Grok Build CLI.
  • Grok Build CLI (Mac / Safari) — static Bearer is the first-class daily path. Do not use the desktop MCP OAuth loopback — known issues.
  • Claude.ai — custom connector + hosted sign-in. Typical read is still get_content → download_url. Claude cannot HTTP GET that URL, so use opt-in get_content_for_llm (small text may use include_content). Do not make inline the default. Do not add delivery= on get_content.

Estes will tell you which of those applies after access review. This site does not publish a self-serve connector secret.

How to read an object

Default typical read: get_content (or retrieve) → HTTP GET the presigned download_url. Only clients that cannot GET that URL use get_content_for_llm. Canonical get_content stays metadata + URL.

Dedicated: bring your own IdP

On a dedicated deployment, Artifactum still speaks Streamable HTTP MCP. You configure the resource server to trust your issuer. Your users sign in with your directory — Google Workspace, Okta, Auth0 you own, or anything that issues the agreed JWT. The vault does not require Estes Auth0 in customer accounts. We have not tested every IdP and do not certify untested directories.

What not to do

  • Do not write runbooks that say “log into Auth0” as if Auth0 were Artifactum.
  • Do not reconnect MCP just to refresh a login if tools still work. Some clients dynamically register a new OAuth app on every connect (known issues).
  • Do not put Bearer tokens in mcp.json committed to git.
  • mcp-grok.artifactum.ai is a dual-mode compatibility host for Grok leftovers — not the brand, and not the default for new clients.