TWS DREX MCP Server
This MCP server provides tools to interact with the DREX document extraction AI API and LoginRadius authentication.
🚀 Get Started
This guide will help you install and run the TWS DREX MCP server.
We recommend using uv to manage your Python environment and run the server.
Install uv
If you don't have uv installed, you can install it by following the instructions on the official documentation: Installation | uv
A common way to install uv is using curl (for Linux/macOS) or by downloading the executable (for Windows):
# For Linux/macOS
curl -fsSL https://astral.sh/uv/install.sh | sh
# For Windows
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Install the TWS DREX MCP Server
Once you have uv installed, you can install the tws-drex-mcp package:
uv pip install tws-drex-mcp
Alternatively, using pip:
pip install tws-drex-mcp
Run the standalone Server
You can run the installed server using uv run:
uv run -m tws_drex_mcp
# or
# uvx tws-drex-mcp
Claude Desktop Configuration
To use the DREX MCP server with Claude Desktop, you need to add it to your Claude Desktop configuration file. The location of this file varies by operating system.
Here is an example configuration for the TWS DREX MCP server:
{
"mcpServers": {
"DREX": {
"command": "uv",
"args": ["tws-drex-mcp"],
"env": {
"DREX_BASE_URL": "<YOUR_DREX_BASE_URL>",
"LR_API_KEY": "<YOUR_LR_API_KEY>",
"LR_API_SECRET": "<YOUR_LR_API_SECRET>"
},
"transportType": "stdio"
}
}
}
Replace <YOUR_DREX_BASE_URL>, <YOUR_LR_API_KEY>, and <YOUR_LR_API_SECRET> with your actual values.
Configuration
Before using the server's tools, ensure the following environment variables are set:
DREX_BASE_URL: The base URL of the target DREX API instance.LR_API_KEY: Your LoginRadius API key.LR_API_SECRET: Your LoginRadius API secret.
The MCP framework will automatically pick up these variables when running the server's tools.
Functionality
The following tools are provided by the server:
get_token: Obtains an authentication token from LoginRadius using a username and password.file_upload: Uploads files to the DREX API.get_status: Retrieves the processing status of a file in the DREX API.get_file_results: Retrieves the processed results of a file in the DREX API.
Usage
get_token
This tool obtains an authentication token from LoginRadius using a username and password.
Example:
{
"username": "your_username",
"password": "your_password"
}
file_upload
This tool uploads files or directories to DREX API. The processing time will take 10 - 80 seconds for each file.
Example:
{
"file_paths": ["path/to/file1.txt", "path/to/dir"],
"uploaded_by": "user_name",
"token": "your_access_token"
}
get_status
This tool retrieves the processing status of a file in the DREX API.
Example:
{
"file_id": "file_id_1",
"token": "your_access_token"
}
get_file_results
This tool retrieves the processed results of a file in the DREX API.
Example:
{
"file_id": "file_id_1",
"token": "your_access_token"
}
LoginRadius Initialization
The LoginRadius SDK is initialized using the LR_API_KEY and LR_API_SECRET environment variables.
Dependencies
The dependencies required to run this server are listed in the pyproject.toml file.
Metadata
Release files for tws-drex-mcp 0.1.20250710.225741
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tws_drex_mcp-0.1.20250710.225741.tar.gz | 40.7 kB | Without provenance | Details for tws_drex_mcp-0.1.20250710.225741.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tws_drex_mcp-0.1.20250710.225741-py3-none-any.whl | Python 3 | none | any | Details for tws_drex_mcp-0.1.20250710.225741-py3-none-any.whl |
Total release size: 49.0 kB
Release files / tws_drex_mcp-0.1.20250710.225741.tar.gz
| Download URL | tws_drex_mcp-0.1.20250710.225741.tar.gz |
|---|---|
| Size | 40.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46b47cdee6829fb7fc64bf4e4410a537b3966f56561db00418da8fa1c9734be0
|
|
BLAKE2b-256 checksum How to use checksums |
26131e54d146277a9b55fd76f01f490d151ec01d81f84c83c43866c32bb38f6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / tws_drex_mcp-0.1.20250710.225741-py3-none-any.whl
| Download URL | tws_drex_mcp-0.1.20250710.225741-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9fd93308958b8e40794812b4d23a80107336264bd67b67549439a074b3ab33d6
|
|
BLAKE2b-256 checksum How to use checksums |
6bf4bfa719e5eeb883d914ed1ca59dcfc21e9196205db41f6d0d3beb3f3e6f2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for tws-drex-mcp 0.1.20250710.225741
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.