tazworks-mcp

# tazworks-mcp An MCP server for the **TazWorks / InstaScreen background screening API** (TazAPI Advanced v2). It lets you place and track background checks, look up clients, products, applicants, orders and results, and reach every other part of the API — from a conversation with Claude, without logging into TazWorks. This is a standalone package. It shares no code with `exclugo-mcp` and has nothing to do with the `taz_apploi` / `taz_rm` integrations inside the Exclugo Django app; it talks to the TazWorks API directly. --- ## This only works from the office The TazWorks application token is locked to the office IP address. The server runs on your own laptop and calls TazWorks directly from it, so TazWorks sees whatever network you are on — not a server somewhere. In the office it works. From home, a hotspot, or anywhere else, it does not. TazWorks won't say "wrong IP" when that happens: calls fail looking like an authentication or connection problem, so check where you are before assuming the token is broken. --- ## Setup You need one thing: a **JWT from an API application** in the [TazWorks Developer Portal](https://developer.tazworks.com). Create an application there, copy its token, and give the same token to everyone who should have access — nobody signs in individually. > **Use a dedicated application, not the token your production integrations use.** TazWorks rate > limits per application (5 requests/second, 20,000/day). Sharing a token means heavy use here can > throttle live ordering, and one compromised laptop means rotating the credential production runs > on. Install [`uv`](https://docs.astral.sh/uv/), then add this to Claude Desktop's config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS): ```json { "mcpServers": { "tazworks": { "command": "uvx", "args": ["tazworks-mcp"], "env": { "TAZ_API_TOKEN": "your.jwt.here" } } } } ``` Restart Claude Desktop. Ask it "what TazWor…