BIA Edge

Connect ChatGPT, Claude, Codex, or another AI tool to BIA Edge

Docs

Connect BIA Edge to your AI tool.

BIA Edge is a remote MCP server. Claude, ChatGPT, and Codex can connect by OAuth; clients that cannot complete OAuth can use an issued API key. Add BIA Edge from the Claude connectors directory or the ChatGPT Plugins Directory, sign in, and start with the setup steps below. No access request or manual approval is required for an individual connection.

The BIA Edge address

Use this addresshttps://mcp.biaedge.com/mcp
Connection typeRemote MCP server
How you get inOAuth sign-in with Google or an emailed code, or an issued API key

Claude: connect from the directory

Directory connectors are available on all Claude plans; custom connectors are also available on Free with a one-connector limit. On Team and Enterprise workspaces, an Owner or Primary Owner must add the organization connector before members connect it.

  1. Open the Connectors Directory

    In Claude, open Customize → Connectors, select the plus button, and browse connectors.

  2. Find BIA Edge

    Search for BIA Edge, open its listing, and select Connect or Install.

  3. Sign in and authorize

    Use Google or an emailed code, authorize the connection, then start a new conversation and ask Claude to use BIA Edge.

If the directory listing is unavailable in a managed workspace, an owner can add https://mcp.biaedge.com/mcp as a custom connector. Leave the client ID and client secret blank so Claude can use BIA Edge’s OAuth discovery. See Anthropic’s current connector instructions.

ChatGPT: connect from the Plugins Directory

BIA Edge is published in ChatGPT’s Plugins Directory, so users can install and connect it without creating a custom developer integration.

  1. Find BIA Edge

    In ChatGPT on the web, desktop, or mobile, open Plugins and search for BIA Edge.

  2. Install and connect

    Open the BIA Edge listing, select the plus button to install it, and connect the included BIA Edge service when prompted. Sign in with Google or an emailed code.

  3. Start a new chat

    Ask ChatGPT to use BIA Edge, or type @BIA Edge, then ask your first immigration-law research question.

Managed workspaces can restrict plugin or app availability. See the current OpenAI plugin instructions.

Other MCP clients: connect manually

If your client supports remote MCP and OAuth but does not have a BIA Edge listing, use the canonical server address directly.

  1. Open connector settings

    Choose the option to add a remote MCP server or custom connector.

  2. Enter the BIA Edge address

    Use https://mcp.biaedge.com/mcp. If the client supports OAuth discovery, leave client ID and client secret fields blank.

  3. Sign in and use it

    Complete OAuth with Google or an emailed code, authorize access, and enable BIA Edge for the conversation.

Codex: connect with OAuth

From a terminal with Codex installed, run:

codex mcp add biaedge --url https://mcp.biaedge.com/mcp
codex mcp login biaedge
codex mcp list

The login command opens the OAuth flow. Sign in with Google or an emailed code. Codex CLI, the Codex IDE extension, and the ChatGPT desktop app share the MCP configuration for the same Codex host. See the current Codex MCP instructions.

API-key fallback

If BIA Edge has issued you a per-user API key, keep it in an environment variable instead of writing the key into a shared configuration file. Codex can use: 

# ~/.codex/config.toml
[mcp_servers.biaedge]
url = "https://mcp.biaedge.com/mcp"
bearer_token_env_var = "BIAEDGE_API_KEY"

Set BIAEDGE_API_KEY in your local environment using the value issued to you. Other MCP clients may use a bearer-token field instead; follow that client’s secret-storage instructions. Keep keys out of source control, screenshots, support emails, and shared configuration files. Contact support if a key may have been exposed.

Getting access

During the pilot, connections are self-service and complimentary for individual practitioners and small teams: add BIA Edge from the Claude connectors directory or the ChatGPT Plugins Directory and sign in with Google or an emailed code. For API keys, firm rollouts, or questions, use the contact form.

What your AI can do once connected

Once connected, your AI can search cases, check ImmCite validity, look through unpublished BIA and AAO decisions, pull statutes and regulations, review state criminal codes for crimmigration questions, find USCIS policy, check visa bulletins, and retrieve specific passages to cite. See the full tool index and how ImmCite validity works.

Data handling

Remote access uses a verified, revocable OAuth identity or an issued API key. Queries are processed to answer the request and operate the service; they are never used to train models by BIA Edge. MCP usage counters retain identity, tool, date, counts, and timing—not raw tool arguments or query text. Operational logs are minimized and ordinarily retained for no more than 90 days. The library is built from public legal materials.

Your AI client may process prompts, MCP tool calls, and tool results under that client's own terms and workspace settings. BIA Edge’s no-training commitment applies only to BIA Edge and does not control the client provider’s retention, training, review, residency, or administrator settings. For confidential client work, use a firm-approved organizational workspace or another no-training account that meets your retention requirements, and avoid client identifiers unless they are necessary and authorized. Details: security and confidentiality, privacy policy, and AI disclaimer.

BIA Edge uses private database networking, purpose-bound runtime roles, managed point-in-time recovery, and a recovery process tested through an isolated restore. The security page describes the current controls and assurance limits.

BIA Edge is a research tool, not legal advice. Verify authorities against the linked primary sources before filing, and review the source and provenance supplied with each result.