Skip to main content

Help

Connect Claude or Codex

Claude Code and Codex can read the Injaz projects you connect, and change the website ones, through the Injaz connector. Every change arrives as a draft you check before it can be published.

Before you connect

  • The assistant sends what it reads, your project’s source included, to its own provider (Anthropic for Claude, OpenAI for Codex). Connect only projects you are happy to share with it.
  • Do not run a build in Injaz while the assistant is writing to the same project. Only one of the two can be saved, and the build may be the one that is lost.
  • A connection cannot publish or spend credits. It reaches only the projects you pick, and any it creates if you allow that.
  • It can change website projects you own, once they have a saved version. Other projects you pick (Android, iPhone, imported from a repository, or shared with others) can be read but not changed.

1. Create a connection

  1. Open Settings, then Assistants.
  2. Under Connect an assistant, give it a name you will recognise, pick the projects, and choose whether it may only read.
  3. If you want, tick May create new projects (not offered while Read only is ticked): it can then start new website projects, up to 5 a day across all your connections. Each starts as an unchecked draft and is added to this connection.
  4. Choose Create connection and copy the token. It is shown once and Injaz keeps no copy; if you lose it, disconnect and create another.

Connector address

https://www.injaz.ai/api/mcp

2. Claude on the web, Desktop or mobile

  1. In Claude, open Settings, then Connectors, and choose Add custom connector.
  2. Name it Injaz and paste the connector address: https://www.injaz.ai/api/mcp
  3. Choose Connect. Injaz opens: sign in if you are asked, pick the projects, and choose Allow.

No token to copy: Claude signs in for you, and the connection appears in Settings, then Assistants, where you can disconnect it.

2a. Claude Code

Run this in a terminal, with your token in place of <token>:

claude mcp add --transport http injaz https://www.injaz.ai/api/mcp --header "Authorization: Bearer <token>"

Add --scope user straight after add to use the connection from every folder. Claude Code keeps the token in its own settings file, so keep that file private.

Run claude mcp list to check that injaz is connected.

2b. Codex

Codex reads the token from an environment variable, so the token never goes into its settings file. Set the variable, then add the connector:

Windows PowerShell

$env:INJAZ_CONNECTOR_TOKEN = "<token>"

macOS or Linux

export INJAZ_CONNECTOR_TOKEN="<token>"
codex mcp add injaz --url https://www.injaz.ai/api/mcp --bearer-token-env-var INJAZ_CONNECTOR_TOKEN

The variable must be set where Codex runs. In PowerShell, $env: lasts only for that window; to keep it, set it once with the command below and open a new window. The Codex app and the IDE extension need the variable in their own environment.

setx INJAZ_CONNECTOR_TOKEN "<token>"

The command writes this entry to ~/.codex/config.toml, which the Codex CLI, app and IDE extension share. You can add it by hand instead:

[mcp_servers.injaz]
url = "https://www.injaz.ai/api/mcp"
bearer_token_env_var = "INJAZ_CONNECTOR_TOKEN"

3. Check what the assistant saved

  • Each save appears in the project’s History as an unchecked draft, with the connection’s name beside it. An open project also shows a notice; Review in History takes you there.
  • On the draft, choose Load it to check if it is offered, then Check it. It runs the same checks a build passes.
  • Or choose Discard it. It brings back the latest version that is not a draft, as a new version; nothing is deleted.
  • An unchecked draft cannot be published until it passes the checks.

What a connection can do

  • List projects, get a project, list files, read files, search files: read the projects you picked. Files that look like they hold a secret key are withheld.
  • List versions, compare versions: see what was saved since you connected, and what changed between two versions. Your own requests to Injaz are never returned.
  • Get a preview picture, where Injaz offers it: see the small picture your browser took of the project’s preview when you last opened it in Injaz. Only a picture taken since you connected, and never for a project that has a database. It can show what you entered in the preview.
  • Write files: change a website project you own. Each save becomes a new unchecked draft in History; nothing is overwritten.
  • Add a picture or font, where Injaz offers it: Injaz fetches one file from a public address the assistant gives and saves it in the project, as an unchecked draft.
  • Discard drafts: take back the drafts this same connection wrote. Nothing is deleted; they stay in History.
  • Get check results: see what the checks found when you checked a draft.
  • Create or duplicate a project: start a new website project, or copy one you picked, only if you allowed it, up to 5 a day in all. A copy has the files only, not the original’s Injaz Cloud, domain or published site.
  • Get this connection: what the connection may do and its limits. Nothing about your account, plan or credits.

No tool publishes, spends credits, turns on Injaz Cloud or changes Android and iPhone projects.

Data and privacy

Injaz keeps each connection, its tokens only as one-way hashes, and one record per request without its content. The assistant sends what it reads to its own provider. The privacy policy has the details: Privacy policy

Support

Questions or problems with the connector: support@injaz.ai

Stop an assistant

Open Settings, then Assistants, and choose Disconnect. The token stops working at once. A connection also expires 90 days after it is made.