Connect your AI assistant to FSOtools.

The connectors

One entry per server FSOtools publishes on this domain, with its status. Live means the address answers today. Planned means it is designed or built but not deployed, so it has no address to add yet; a planned connector gains its connect command here on the day it goes live.

• Live
• Planned

Adjudication Atlas Live

Searches, compares and counts the published DOHA security-clearance decisions in the Adjudication Atlas: case number, date, guidelines, cited SEAD 4 conditions and outcome, the Atlas's statistics with their confidence intervals, and a search of the decisions' words that returns short passages, every result linked to the official decision on DOHA's site.

Address	https://fsotools.ai/atlas/mcp (Streamable HTTP). Opened in a browser, the address shows a guide to its eight tools.
Claude Code	claude mcp add --transport http doha-atlas https://fsotools.ai/atlas/mcp
Claude.ai	Settings → Connectors → Add custom connector. Name it Adjudication Atlas, paste the address and save.
ChatGPT	Settings → Apps & Connectors → Advanced → turn on Developer mode (paid plans), then Create. Name it Adjudication Atlas, paste the address, choose No authentication and save. Its search and fetch tools also serve ChatGPT's deep research and company-knowledge modes.
Antigravity	Add "doha-atlas": { "serverUrl": "https://fsotools.ai/atlas/mcp" } to Antigravity's mcp_config.json. The Antigravity steps below show where that file is in the program, the block for all four connectors, and how to check the connection.
Open models	Any client that takes a remote MCP address, whatever model it runs (Llama, Mistral, Qwen …): Open WebUI under External Tools (type MCP (Streamable HTTP)), LM Studio in mcp.json with a url entry, Codex CLI or Gemini CLI in their MCP settings. Same address, no key.
Privacy	Stateless: it issues no session and keeps none. Request logging is switched off in the Worker, so no record of what was asked exists. The only limit is 60 requests a minute from one network address. It answers from published decisions only: no applicant details, no case narratives, and it predicts nothing.
Product page	Adjudication Atlas, served by the doha-atlas-mcp Worker on this domain.

FSO Question Bot Live

Answers a Facility Security Officer's compliance question with cited passages from the approved DCSA library release (32 CFR Part 117, ISLs, DCSA and ODNI publications), a reviewed Knowledge Desk answer where one matches, and related published DOHA decisions. It never composes an answer itself: your assistant does, from the citations it returns.

Address	https://fsotools.ai/question-bot/mcp (Streamable HTTP). Opened in a browser, the address shows a guide to its nine tools.
Claude Code	claude mcp add --transport http fso-question-bot https://fsotools.ai/question-bot/mcp
Claude.ai	Settings → Connectors → Add custom connector. Name it FSO Question Bot, paste the address and save.
ChatGPT	Settings → Apps & Connectors → Advanced → turn on Developer mode (paid plans), then Create. Name it FSO Question Bot, paste the address, choose No authentication and save. Its search and fetch tools also serve ChatGPT's deep research and company-knowledge modes.
Antigravity	Add "fso-question-bot": { "serverUrl": "https://fsotools.ai/question-bot/mcp" } to Antigravity's mcp_config.json. The Antigravity steps below show where that file is in the program, the block for all four connectors, and how to check the connection.
Open models	Any client that takes a remote MCP address, whatever model it runs (Llama, Mistral, Qwen …): Open WebUI under External Tools (type MCP (Streamable HTTP)), LM Studio in mcp.json with a url entry, Codex CLI or Gemini CLI in their MCP settings. Same address, no key.
Privacy	Stateless: it issues no session and keeps none, and request logging is switched off in the Worker. The limit is 60 requests a minute from one network address. Every result carries its citation (document, passage, official link), so nothing is quoted without a source. One tool is different by design: if you choose to offer a researched answer to the Knowledge Desk, the connector asks for your consent and the name and e-mail to credit, and holds that submission for the maintainer's review. Nothing is stored unless you say yes.
Product page	FSO Knowledge Desk, which publishes its accepted answers; the projects page lists the Question Bot itself. Served by the fso-question-bot-mcp Worker on this domain.

Adverse Information Assistant Live

Reference material for someone preparing an adverse-information self-report: which SEAD 3 reporting table applies, the text of the SEAD 4 guideline and conditions a report will be measured against, and the maintainer's checklists and form maps. The report itself is prepared in your own assistant, which never has to send the server a word of your situation.

Address	https://fsotools.ai/adverse/mcp (Streamable HTTP). Opened in a browser, the address shows a guide to its seventeen tools and the product's disclaimer.
Claude Code	claude mcp add --transport http adverse-information-assistant https://fsotools.ai/adverse/mcp
Claude.ai	Settings → Connectors → Add custom connector. Name it Adverse Information Assistant, paste the address and save.
ChatGPT	Settings → Apps & Connectors → Advanced → turn on Developer mode (paid plans), then Create. Name it Adverse Information Assistant, paste the address, choose No authentication and save. ChatGPT's chat mode can call its tools; its deep research mode is not served, because this connector has no search and fetch tools.
Antigravity	Add "adverse-information-assistant": { "serverUrl": "https://fsotools.ai/adverse/mcp" } to Antigravity's mcp_config.json. The Antigravity steps below show where that file is in the program, the block for all four connectors, and how to check the connection.
Open models	Any client that takes a remote MCP address, whatever model it runs (Llama, Mistral, Qwen …): Open WebUI under External Tools (type MCP (Streamable HTTP)), LM Studio in mcp.json with a url entry, Codex CLI or Gemini CLI in their MCP settings. Same address, no key.
Privacy	Stateless, with no request logs and no sessions, and stricter than the other two: no free text at all. Every request is a code from a published list (a guideline letter, an access level, an event type), so there is nothing about your matter that the server could receive, let alone keep. The only limit is 60 requests a minute from one network address.
Product page	Adverse Information Assistant on GitHub ↗ (open source), served by the adverse-information-assistant Worker on this domain.

Security Clearance Question Bot Live

Answers a person's security clearance question with cited passages from the approved DCSA library release: the Security Executive Agent Directives, 32 CFR Part 117, the DoD personnel security issuances and DCSA guidance, the SEAD 4 adjudicative guideline the question raises, and related published DOHA decisions. It answers only security clearance questions: a Special Access Program or Sensitive Compartmented Information question gets a fixed reply that it is not trained in SAP or SCI, and a facility or NISP question is sent to the FSO Question Bot. It never composes an answer itself: your assistant does, from the citations it returns.

Address	https://fsotools.ai/clearance/mcp (Streamable HTTP). Opened in a browser, the address shows a guide to its nine tools and the scope rule it applies.
Claude Code	claude mcp add --transport http clearance-question-bot https://fsotools.ai/clearance/mcp
Claude.ai	Settings → Connectors → Add custom connector. Name it Security Clearance Question Bot, paste the address and save.
ChatGPT	Settings → Apps & Connectors → Advanced → turn on Developer mode (paid plans), then Create. Name it Security Clearance Question Bot, paste the address, choose No authentication and save. Its search and fetch tools also serve ChatGPT's deep research and company-knowledge modes.
Antigravity	Add "clearance-question-bot": { "serverUrl": "https://fsotools.ai/clearance/mcp" } to Antigravity's mcp_config.json. The Antigravity steps below show where that file is in the program, the block for all four connectors, and how to check the connection.
Open models	Any client that takes a remote MCP address, whatever model it runs (Llama, Mistral, Qwen …): Open WebUI under External Tools (type MCP (Streamable HTTP)), LM Studio in mcp.json with a url entry, Codex CLI or Gemini CLI in their MCP settings. Same address, no key.
Privacy	Stateless: it issues no session and keeps none, and request logging is switched off in the Worker. The limit is 60 requests a minute from one network address. Every result carries its citation (document, passage, official link); nothing is written anywhere; and it applies the same published scope rule as the local Security Clearance Question Bot, so a question it will not answer is refused the same way in both places.
Product page	Security clearance process map, served by the clearance-question-mcp Worker on this domain.

Google Antigravity, step by step

Antigravity is Google's agent-first coding program. These steps are for the Antigravity application on your computer and the editor and agent panel it opens; nothing here uses a command line. Antigravity keeps its MCP servers in a settings file, and a server that is not in its built-in store, such as these connectors, is added by editing that file.

1. Open the MCP settings file

• From the agent panel: click the … menu at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config. The settings file opens in the editor.
• From Settings: click Settings at the bottom left, choose Customizations and find Installed MCP Servers. Its Add MCP button opens Antigravity's MCP Store, a catalogue of servers Google lists. These connectors are not in the store, so use the raw config route above to add them; this view is where you see, pause or remove them afterwards.

If neither route shows the file, open it directly. It is mcp_config.json in the .gemini\config folder of your home folder: on Windows C:\Users\<you>\.gemini\config\mcp_config.json, on a Mac ~/.gemini/config/mcp_config.json. Create it if it does not exist. A file named .agents/mcp_config.json inside a project folder does the same for that project only.

2. Add the connectors

Paste this in and save. If the file already has an mcpServers block, add the entries inside it rather than pasting a second block; keep only the connectors you want.

{
  "mcpServers": {
    "doha-atlas": {
      "serverUrl": "https://fsotools.ai/atlas/mcp"
    },
    "fso-question-bot": {
      "serverUrl": "https://fsotools.ai/question-bot/mcp"
    },
    "adverse-information-assistant": {
      "serverUrl": "https://fsotools.ai/adverse/mcp"
    },
    "clearance-question-bot": {
      "serverUrl": "https://fsotools.ai/clearance/mcp"
    }
  }
}

serverUrl is Antigravity's name for a remote server's address (url is accepted too; httpUrl is not). No headers, token or sign-in is needed, because these connectors take none.

3. Check that they connected

• In Settings → Customizations → Installed MCP Servers, each connector should be listed with its switch on. The refresh button reloads the file if a new entry has not appeared; the switch pauses a server without removing it; the trash can removes it.
• Then ask the agent something a connector answers, in plain words, for example: Using the Adjudication Atlas, find hearing decisions under Guideline F from 2024 where the clearance was granted. There is no special command: the agent picks the connector's tool and shows you the call.

4. The approval prompt

Antigravity treats every MCP tool as unapproved until you say otherwise, so the first calls arrive as Ask prompts: approve each one, or allow the server in its permission settings. The rule mcp(doha-atlas/*) allows every tool of that connector and mcp(*) allows all MCP tools. Every tool here declares itself read-only, and allowing them changes nothing on this side: the connectors still store nothing.

If something is off

• Not listed after saving: check for a stray comma and that the entry sits inside mcpServers, then press refresh.
• Shown as disconnected: the address must be exactly as above, with https. The connectors speak plain MCP over Streamable HTTP, which is what Antigravity sends; there is nothing else to configure. An entry with "disabled": true is switched off; remove that line to turn it back on.
• A call times out: Antigravity allows 300 seconds to connect and 180 per call by default, and "timeoutSeconds": 600 on an entry raises both. The connectors answer in well under a second, so a timeout points at the network between you and them.