Host Setup

Host Setup

Ten hosts, plus a remote HTTP mode for shared infrastructure. Every stdio host runs the same command, npx -y @intempt-technologies/mcp, and differs only in where the config file lives and what the top-level key is called.

Replace your-org and your-project with your own slugs. If your account belongs to exactly one of each, you can omit both and let login resolve them.

Claude Code

The plugin is the shortest path. It registers the server and bundles a setup skill that handles install, login and org selection in one step.

/plugin marketplace add intempt/intempt-claude-plugin
/plugin install intempt@intempt-plugins

Restart Claude Code, then say run intempt setup.

Manual alternative:

claude mcp add intempt -- npx -y @intempt-technologies/mcp

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows:

{
  "mcpServers": {
    "intempt": {
      "command": "npx",
      "args": ["-y", "@intempt-technologies/mcp"],
      "env": {
        "INTEMPT_ORG": "your-org",
        "INTEMPT_PROJECT": "your-project"
      }
    }
  }
}

Cursor

Cursor Settings, then MCP Servers, then Add:

{
  "mcpServers": {
    "intempt": {
      "command": "npx",
      "args": ["-y", "@intempt-technologies/mcp"],
      "env": {
        "INTEMPT_ORG": "your-org",
        "INTEMPT_PROJECT": "your-project"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json, same shape as Cursor.

VS Code (GitHub Copilot)

Add to your workspace .vscode/mcp.json. Note the key is servers, not mcpServers:

{
  "servers": {
    "intempt": {
      "command": "npx",
      "args": ["-y", "@intempt-technologies/mcp"],
      "env": {
        "INTEMPT_ORG": "your-org",
        "INTEMPT_PROJECT": "your-project"
      }
    }
  }
}

Zed

Edit ~/.config/zed/settings.json. Zed nests the command differently from everyone else:

{
  "context_servers": {
    "intempt": {
      "command": {
        "path": "npx",
        "args": ["-y", "@intempt-technologies/mcp"],
        "env": {
          "INTEMPT_ORG": "your-org",
          "INTEMPT_PROJECT": "your-project"
        }
      }
    }
  }
}

Cline

Cline Settings, then MCP Servers, then Add Custom Server. Same shape as Cursor.

Codex (OpenAI)

Codex CLI reads MCP servers from ~/.codex/config.toml. The top-level table is mcp_servers with an underscore, and each server is its own sub-table. The Codex CLI and the Codex VS Code extension share this file.

[mcp_servers.intempt]
command = "npx"
args = ["-y", "@intempt-technologies/mcp"]

[mcp_servers.intempt.env]
INTEMPT_ORG = "your-org"
INTEMPT_PROJECT = "your-project"

Or let the CLI write the table for you:

codex mcp add intempt -- npx -y @intempt-technologies/mcp

To reach Intempt from the ChatGPT app's Developer Mode connectors instead of a local CLI, run the server in remote mode and add its URL as a connector.

Gemini CLI

Edit ~/.gemini/settings.json. The top-level key is mcpServers, the same shape as Cursor:

{
  "mcpServers": {
    "intempt": {
      "command": "npx",
      "args": ["-y", "@intempt-technologies/mcp"],
      "env": {
        "INTEMPT_ORG": "your-org",
        "INTEMPT_PROJECT": "your-project"
      }
    }
  }
}

Restart the CLI and run /mcp to confirm the tools registered. gemini mcp list shows the same from the shell.

Google Antigravity

Antigravity keeps MCP servers in a file named mcp_config.json under ~/.gemini/. The exact path has moved between releases, so open it from the IDE rather than guessing: in the MCP settings, use Open MCP Config. The MCP Store in the IDE can also add a server without editing the file.

Entries go under mcpServers, with a local server defined by command and args:

{
  "mcpServers": {
    "intempt": {
      "command": "npx",
      "args": ["-y", "@intempt-technologies/mcp"],
      "env": {
        "INTEMPT_ORG": "your-org",
        "INTEMPT_PROJECT": "your-project"
      }
    }
  }
}

A remote server uses serverUrl here instead of command, which differs from the Cursor and VS Code configs. Save, then click refresh in the Installed MCP Servers section.

Remote mode over HTTP

For shared infrastructure, multi-user setups, or Claude Connectors. This runs an HTTP server with OAuth 2.1 and PKCE instead of speaking stdio to a local host.

MCP_TRANSPORT=http MCP_PORT=3010 npx @intempt-technologies/mcp

Extra variables for this mode:

In a container

docker run -p 3010:3010 \
  -e INTEMPT_ORG=your-org \
  -e INTEMPT_PROJECT=your-project \
  intempt-mcp

Authentication in automation

Interactive login needs a browser, which CI does not have. Set INTEMPT_AUTH_TOKEN to a static JWT instead and the server skips the interactive flow entirely.

After setup

A fresh install serves 67 tools. See MCP Server for how to widen that with INTEMPT_MCP_TOOLS, and Limits for what the server will not do at any setting.