Connect

How you get in

Use your Hosted vault address, such as https://YOUR-VAULT.mcp.artifactum.ai/, provided during setup. You sign in as yourself. One email is one person. Do not share a login or access key.

ChatGPT uses your dedicated vault address — not the shared host unless that is the address provided for your account. Claude, Grok, and the browser on the web: add that address and sign in when asked. Cursor and Grok Build CLI need your access key, not a teammate’s.

ChatGPT

Create an Artifactum custom MCP app on ChatGPT web from Settings → Apps → Create. In some managed workspaces, an administrator must enable Developer mode or publish the app first. The Plugins directory now lists plugins and workflows; it is not the current custom-app creation path. Artifactum works with ChatGPT Plus. Add the custom app on ChatGPT web, then select it in a conversation to save and find files. Managed workspaces may require an administrator to enable Developer mode or approve the app. OpenAI currently documents custom MCP apps on web; see the complete ChatGPT setup. Full steps and MFA/security notes: ChatGPT setup.

Browser vault

Open app.artifactum.ai and sign in. This is a first-party browser for viewing the same files your connected AIs can access. It is separate from your private MCP address.

Cursor app and CLI

Cursor’s Customize → MCP page can add a server, or configure it in ~/.cursor/mcp.json. Use your vault address and put the access key in an environment variable referenced by the config. Restart Cursor after saving. The editor app and CLI are separate processes; make sure the key is available to the one you use. Follow the Cursor setup.

Grok Bot

In the Grok Bot app, open the Bot’s info pane and use its Setup → Plugins card to add a remote HTTPS custom MCP server. Paste the vault address and complete its sign-in. For a Team Bot, the owner adds the shared plugin; a personal connector may use your own sign-in. After setup, test in a one-to-one Bot chat. xAI’s Team Bots guide describes remote custom MCP plugins, and its team guide explains connector policy. If your app doesn’t show a custom MCP option, ask its team admin to check the connector policy.

Grok web and iPhone

On the web, open grok.com/connectors and select New Connector → Custom.
Paste your vault address, follow the authentication steps, and save the connector.
In a Grok conversation, choose the Artifactum connector when you want Grok to use it. On iPhone, sign in to the same Grok account and select the saved connector if it is available in the app.

On Grok Business or Enterprise, an admin must provision the custom connector in console.x.ai → Grok Business → Connectors first. xAI’s current custom connector guide lists the personal web path; its team admin guide lists workspace setup. Artifactum’s Grok connection is tested on web and iPhone.

Grok Build CLI

The CLI uses a personal access key. Current xAI Grok Build supports HTTP MCP servers and expands environment variables in header values. Keep the key in your local secret store or shell environment; don’t paste it into a project file or commit it.

# Add to ~/.grok/config.toml
[mcp_servers.artifactum]
url = "https://YOUR-VAULT.mcp.artifactum.ai/"
headers = { Authorization = "Bearer ${ARTIFACTUM_MCP_BEARER}" }

Set ARTIFACTUM_MCP_BEARER in the environment before launching Grok, then run grok mcp doctor artifactum or grok mcp list to verify. In the TUI, use /mcps to view or refresh connections. xAI’s Grok Build MCP guide has the current command and configuration options. Safari can interrupt a separate browser login loop; the access-key setup above does not require that login flow.

Claude web and Claude Desktop

Claude’s remote custom connectors work through your Claude account in the web and desktop apps. Open Customize → Connectors → + Add → Add custom connector, enter a name and your vault address, then continue through the detected authentication settings. Choose the OAuth client option specified in your Artifactum setup email, complete Artifactum sign-in, and select the connector in a conversation. If Claude Desktop offers Settings → Connectors, it manages the same account-level remote connector. Local Desktop extensions are a separate feature and are not needed for Artifactum. Team/Enterprise owners must add the connector under Organization settings → Connectors before members connect it. See Anthropic’s remote connector instructions and web vs desktop connector guide.

Claude can use the vault tools, but may not be able to open Artifactum’s short-lived file download links. For supported reading paths, see known issues.

Claude Code

Claude Code supports remote HTTP MCP from the command line. Set the access key in a secure environment variable, then add the server at user scope so it is available across projects:

claude mcp add --transport http --scope user artifactum \
  https://YOUR-VAULT.mcp.artifactum.ai/ \
  --header "Authorization: Bearer ${ARTIFACTUM_MCP_BEARER}"

claude mcp list

Keep the personal config private and never add a live key to a project’s .mcp.json. In Claude Code, use /mcp to check the connection and follow the sign-in prompt if your server uses OAuth. See Anthropic’s Claude Code MCP guide.

Codex

Codex CLI, the IDE extension, and the desktop app share MCP settings. Put this in ~/.codex/config.toml, then make the access key available to the environment that launches Codex:

[mcp_servers.artifactum]
url = "https://YOUR-VAULT.mcp.artifactum.ai/"
bearer_token_env_var = "ARTIFACTUM_MCP_BEARER"

Run codex mcp list or enter /mcp in the Codex TUI to check it. The access key authenticates to Artifactum; sign in to Codex separately with your OpenAI account. The same config is used by the supported Codex clients. See the official Codex MCP guide.

Hermes Agent CLI

Hermes Agent supports remote HTTP MCP. Run hermes mcp add artifactum --url https://YOUR-VAULT.mcp.artifactum.ai/ --auth header and follow the prompt to save your access key. The CLI stores the key in its local environment file and writes only an environment-variable reference in the server config. Then verify with hermes mcp test artifactum and restart or reload MCP in Hermes. The detailed Hermes setup includes a configuration-file option. See the official Hermes MCP guide.

Other apps that support MCP

Artifactum uses the open Model Context Protocol (MCP). Most other apps that support remote MCP over HTTP should work too. Use the vault address and the authentication method your setup email specifies (OAuth or an access key in the Authorization: Bearer header). If your app offers a Streamable HTTP option, choose it. The service must be reachable at its public HTTPS address; local-only servers need an approved tunnel. See tested clients and known limits, and tell us if another MCP client gives you trouble.

Dedicated

Same product on your AWS, with your company’s sign-in. That’s a conversation — contact us.