opteryx-mcp

# opteryx-mcp Connect Claude Desktop, Claude Code and other MCP clients to [Opteryx](https://opteryx.app). Ask questions about your data in plain English; the assistant finds datasets, reads schemas, queries, and checks Opteryx SQL, all as you and against only the data you can see. ```bash uvx opteryx-mcp login --user <user> ``` ## Why a local bridge The Opteryx MCP endpoint (`https://agent.opteryx.app/mcp/`) takes a bearer token, and access tokens last five minutes. A token pasted into a client's config stops working almost immediately. `opteryx-mcp` holds a **user** and a **personal access token** instead, exchanges them for a fresh access token a minute before each one expires, and forwards everything the client sends. It also re-mints if a token is rejected, and re-opens the MCP session if the server forgets it. It has no dependencies beyond the Python standard library. ## Setup ### 1. Create a personal access token In Opteryx Studio, open **Settings** and create a personal access token. It looks like `opt_..._01`, lasts 90 days by default, and is shown once. ### 2. Store it On macOS, `login` stores the token in the Keychain and checks it works. `security` prompts for the token, so it never appears in shell history: ```bash uvx opteryx-mcp login --user <user> ``` ``` Connected to https://agent.opteryx.app/mcp/ as <user>. 7 tools: search_datasets, get_dataset_schema, query_dataset, profile_column, lookup_sql_syntax, search_docs, validate_sql ``` Run it again to replace an expired token. On other platforms, set `OPTERYX_TOKEN` in the client's config instead. ### 3. Add it to your client **Claude Desktop.** Print the config entry: ```bash uvx opteryx-mcp config --user <user> ``` Then **quit Claude Desktop (Cmd-Q)** and merge the entry into `~/Library/Application Support/Claude/claude_desktop_config.json`, keeping the file's other keys. Desktop rewrites that file when it quits, so an entry added while it is running is silently dropped. The entry lo…