Request access and receive an approved account
Island Intel JA opens through guided access first. Approved accounts receive a workspace and starter plan scope before any connector is enabled.
Connector path / approved accounts only
Connect Island Intel JA
to Claude.
Your preferred AI client — Claude, Codex, ChatGPT, or a custom host — becomes procurement-aware when connected through Island Intel’s approved connector.
MCP (Model Context Protocol) is the secure tool rail that lets a compatible AI ask Island Intel for approved procurement intelligence instead of guessing from training data. Your client receives only the tools your plan allows. Official documents control.
Prerequisite: Connection requires an approved Island Intel JA account. Accounts open through the guided private pilot — not public self-serve. Submitting a request does not activate billing.
Agent access does not grant legal advice, bid advice, eligibility certification, compliance certification, raw system access, privileged credentials, or government authority. Island Intel JA is an independent private service and is not affiliated with the Office of Public Procurement or any government body.
Connection flow
Scoped access before any agent moves.
Open the MCP connection panel inside your account
Choose the AI client host you want to connect: Claude custom connector, Codex, ChatGPT, or another MCP-compatible host.
Authorise the connection through OAuth 2.1
Approve the connection through OAuth. Use a show-once bearer token fallback only where the host requires it. Credentials stay revocable.
Your AI agent works within your account
The agent inherits your plan, rate limits, tool entitlements, and document-access boundary automatically.
Connection topology / single boundary
One account boundary. Many AI clients.
GOJEP tendersnotices / deadlines / docs
Legal provisionsacts / rules / thresholds
RFP documentsSBDs / addenda / BOQs
Supplier recordsPPC / NCC / registry
Award historycontracts / entities / values
›
›
Claude Desktopcompatible remote connector
CodexStreamable HTTP
ChatGPT connectorStreamable HTTP
Custom MCP hostStreamable HTTP
The account boundary enforces plan limits, tool entitlements, and revocation before any tool call reaches the estate.
Technical posture
What the connection does.
- Connection protocol
- OAuth 2.1 with show-once bearer-token fallback for hosts that require it.
- Tool surface
- Customer-safe tool profile only. Operations observability and write paths never appear.
- Scope inheritance
- Agent inherits the account plan, rate limits, tool entitlements, and brief-family access.
- Revocation
- Revoke any connection from the account connection panel before the next tool call.
- Telemetry
- Every allowed or denied agent tool call appears in the customer's usage view.
- Boundary
- Agents never receive infrastructure access, private infrastructure details, or privileged credentials.
ready to connect
Start with an approved account.
Request access to begin the private pilot review. Once approved, workspace setup and connector instructions follow. No billing activation before review.