Connect a coding agent to Access360

Add Access360 to Claude Code or OpenAI Codex, so an agent working in your terminal or pipeline can read and change Process Design content.

Prerequisites

Requires Access360 to be set up for your platform, and your platform's MCP Server URL. Your iGrafx administrator copies the URL from Admin → Server Settings → AI Settings and gives it to you. See step 6 of Set up Access360.
Requires an iGrafx account with the Access MCP server permission. The agent can do exactly what that account can do. See Access360 access controls.
For an agent that runs unattended, requires an API key for that account and Allow access via API Key turned on. Give the agent its own account with only the permissions its task needs. See Individual and shared accounts.

Supported versions

Both clients connect to Access360 over Streamable HTTP. The commands below follow the clients' own documentation: Claude Code MCP and Codex MCP.

Configuration

Choose how the agent signs in:

Interactive sign-in — you sign in once in a browser with your iGrafx account, the same way as in a chat assistant. Use this when the agent works for you.
API key in a header — the agent sends the key with every request. Nothing opens in a browser, so this is the way for backend services, pipelines, and other unattended runs.

In the examples below, replace the whole address with your MCP Server URL: <region> is com, eu, or jp, and <tenant-id> is your platform's tenant ID. Keep the API key in an environment variable, such as IGRAFX_API_KEY, rather than in a file you commit.

Claude Code

Interactive sign-in:

Add the server:

claude mcp add --transport http igrafx https://process-design-mcp.svc.igrafxcloud.<region>/<tenant-id>

In Claude Code, run /mcp, select igrafx, and sign in on the iGrafx authorization page that opens.

For an API key in a header, add the server to the project's .mcp.json instead. Claude Code fills in ${IGRAFX_API_KEY} from the environment when it starts:

{
  "mcpServers": {
    "igrafx": {
      "type": "http",
      "url": "https://process-design-mcp.svc.igrafxcloud.<region>/<tenant-id>",
      "headers": { "Authorization": "Bearer ${IGRAFX_API_KEY}" }
    }
  }
}

Codex

Interactive sign-in:

Add the server:

codex mcp add igrafx --url https://process-design-mcp.svc.igrafxcloud.<region>/<tenant-id>

For an API key in a header, add the server to ~/.codex/config.toml instead. Codex reads the key from the environment variable you name:

[mcp_servers.igrafx]
url = "https://process-design-mcp.svc.igrafxcloud.<region>/<tenant-id>"
bearer_token_env_var = "IGRAFX_API_KEY"

Verify

Ask the agent: "Which iGrafx user are you connected as?" It answers with the name of the account behind the sign-in or the key.

Troubleshooting

Requests fail with 401 — the key is wrong, deleted, or missing from the environment, or an interactive sign-in has expired after 90 days. Check the variable, or sign in again.
The agent reports that MCP connectivity is disabled, or that the account doesn't have permission — compare the message with Messages an assistant reports.
The agent can't add files to the repository — adding files needs interactive sign-in. With an API key in the header, the agent can read stored files but not upload new ones.

Access360
How Access360 signs in
Access the REST API, for integrations that call Process Design directly instead of through an agent

Prerequisites​

Supported versions​

Configuration​

Claude Code​

Codex​

Verify​

Troubleshooting​

Related​