Connect your agent

Any MCP client that can talk to a remote HTTP server and send an Authorization header can connect to Prophouse. You need an API key and one line of configuration.

Create an API key

Sign in at app.prophouse.dev and open API keys.
Under Create key, give the key a Name you will recognize later (for example claude-code-laptop).
Pick a Scope. Choose write if the agent should check props in, act on reviews, comment or import into Unreal. Choose read for an agent that only searches and downloads.
Click Create key and copy the key. It starts with ph_live_ and is shown only once.

Treat the key like a password. If it leaks, click Revoke next to it on the API keys page and create a new one.

Add the server to your client

The server URL is https://api.prophouse.dev/mcp for every workspace. Replace ph_live_xxxxxxxxxxxx below with your key.

Run:

claude mcp add --transport http prophouse https://api.prophouse.dev/mcp --header "Authorization: Bearer ph_live_xxxxxxxxxxxx"

This adds the server for the current project only. Add --scope user to make it available in every project.

To share the server with your team through a checked-in .mcp.json, keep the key out of the file and read it from an environment variable instead:

{
  "mcpServers": {
    "prophouse": {
      "type": "http",
      "url": "https://api.prophouse.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${PROPHOUSE_API_KEY}"
      }
    }
  }
}

Each person then sets PROPHOUSE_API_KEY to their own key (see the Codex tab for how to set it on each OS). Run /mcp inside Claude Code to check that prophouse is connected.

Codex reads the key from an environment variable. Add the server:

codex mcp add prophouse --url https://api.prophouse.dev/mcp --bearer-token-env-var PROPHOUSE_API_KEY

That writes this entry to ~/.codex/config.toml, which you can also add by hand:

[mcp_servers.prophouse]
url = "https://api.prophouse.dev/mcp"
bearer_token_env_var = "PROPHOUSE_API_KEY"

Then set PROPHOUSE_API_KEY to your key:

In PowerShell, store it for your user account:

[Environment]::SetEnvironmentVariable("PROPHOUSE_API_KEY", "ph_live_xxxxxxxxxxxx", "User")

Close and reopen your terminal (and restart Codex) so it picks up the new variable.

Add it to your shell profile (zsh is the default shell):

echo 'export PROPHOUSE_API_KEY="ph_live_xxxxxxxxxxxx"' >> ~/.zshrc
source ~/.zshrc

Add it to your shell profile (bash shown):

echo 'export PROPHOUSE_API_KEY="ph_live_xxxxxxxxxxxx"' >> ~/.bashrc
source ~/.bashrc

Start Codex from a terminal that has the variable set.

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "prophouse": {
      "url": "https://api.prophouse.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PROPHOUSE_API_KEY}"
      }
    }
  }
}

${env:PROPHOUSE_API_KEY} reads the key from an environment variable, so the file holds no secret (see the Codex tab for how to set one on each OS). You can paste the key in place of the variable instead, but then keep that file out of version control.

Configure a remote MCP server with:

Setting	Value
Transport	Streamable HTTP (sometimes labeled “HTTP”)
URL	`https://api.prophouse.dev/mcp`
Header	`Authorization: Bearer ph_live_xxxxxxxxxxxx`

The server answers every request with plain JSON and never opens an event stream, so clients that only support the older SSE transport cannot connect. GET and DELETE on the endpoint return 405.

Check the connection

Ask the agent to “call the Prophouse whoami tool”. It should report your member name, your role and the key’s scopes. If the client reports 401, the key is wrong or revoked. If write tools fail with FORBIDDEN, the key is read-only.

The server sends its own usage guidance to the agent when it connects, so most agents know to start with whoami, use filters, and respect locks without extra prompting.