TrueScreen supports MCP integrations in addition to the REST Public API. This lets AI clients such as Cursor or Claude Desktop call curated TrueScreen operations directly, without building raw HTTP requests by hand.
TrueScreen provides two MCP servers:
- a remote MCP server for text and JSON operations,
- a local MCP server for the same operations plus flows that need file uploads from your machine.
| Use case | Remote MCP | Local MCP |
|---|---|---|
| Get credits | Yes | Yes |
| List available templates | Yes | Yes |
| Create a True Flow without local file upload | Yes | Yes |
| Create a hash certification | Yes | Yes |
| Check certification status | Yes | Yes |
| Wait for certification completion | Yes | Yes |
| Create a file certification from files on disk | No | Yes |
| Upload a True Flow attachment from files on disk | No | Yes |
In practice:
- Use the remote MCP server when your workflow is fully text or JSON based.
- Use the local MCP server when the workflow includes a file that must be read from your machine and uploaded.
These tools are available on both the remote and local server:
truescreen_get_creditstruescreen_list_templatestruescreen_create_true_flowtruescreen_create_hash_certificationtruescreen_get_certificationtruescreen_wait_for_certification
These tools are available only on the local server:
truescreen_create_file_certification_attachmentstruescreen_upload_filetruescreen_create_file_certificationtruescreen_create_true_flow_attachment
Use the local server when you need:
- file certification, because the workflow includes file upload,
- True Flow attachments, because the file must be read locally before upload.
Each MCP tool maps to one or more Public API calls. Use this table to move between the MCP surface and the corresponding REST documentation.
| MCP tool | REST call | REST documentation |
|---|---|---|
truescreen_get_credits | GET /v1/credits | Certification overview - Credits |
truescreen_list_templates | GET /v1/templates | True Flow call flow - Flow template token |
truescreen_create_true_flow | POST /v1/true-flows | True Flow call flow - Use cases |
truescreen_create_hash_certification | POST /v1/hash-certifications | Certification call flow - Hash certification |
truescreen_get_certification | GET /v1/certifications/{reportId} | Certification call flow - Checking certification status |
truescreen_wait_for_certification | Polling GET /v1/certifications/{reportId} | Certification overview - Asynchronous process |
truescreen_create_file_certification_attachments | POST /v1/file-certifications-attachments | Certification call flow - File certification |
truescreen_upload_file | PUT upload_url on the presigned URL returned by the API | Certification call flow - Step 2 upload the files |
truescreen_create_file_certification | POST /v1/file-certifications | Certification call flow - File certification |
truescreen_create_true_flow_attachment | POST /v1/true-flows-attachments and PUT upload_url before POST /v1/true-flows | True Flow call flow - True Flow creation with attachments |
If you need the schema-level contract for any of these calls, use the OpenAPI spec alongside the workflow guides.
The remote server is the simplest option when you do not need local file access. You configure your MCP client with the TrueScreen MCP URL and the same API key you use for the REST API.
- A valid TrueScreen API key
- An MCP client that supports Streamable HTTP
Add this to your mcp.json:
{
"mcpServers": {
"truescreen": {
"url": "https://mcp.truescreen.app/mcp",
"headers": {
"Authorization": "Bearer abc..."
}
}
}
}- The API key is sent in the
Authorizationheader as a Bearer token. - No local Node.js process is required.
- Any MCP client with equivalent URL and header configuration can use the same remote server.
The local server runs as a Node.js process on your machine. It is the right choice when the workflow needs files from disk.
- A valid TrueScreen API key
- Node.js 20 or later
Add this to your mcp.json:
{
"mcpServers": {
"truescreen-local": {
"command": "npx",
"args": ["-y", "@truescreen/mcp"],
"env": {
"TRUESCREEN_API_KEY": "abc..."
}
}
}
}If you need a non-production environment, you can also set MCP_ENV tovstg.
{
"mcpServers": {
"truescreen-local": {
"command": "npx",
"args": ["-y", "@truescreen/mcp"],
"env": {
"TRUESCREEN_API_KEY": "abc...",
"MCP_ENV": "stg"
}
}
}
}- Use the local server as a package executed by the MCP client, typically with
npx -y @truescreen/mcp. - In normal usage you do not install it into your application with
npm i @truescreen/mcp. - The local package name is
@truescreen/mcp. - The client starts the process for you; you do not need to run a separate daemon manually.
- The same MCP client can be configured with both the remote and local server at the same time.
Use remote MCP when you want the fastest setup and your workflow does not upload files.
Use local MCP when you want to:
- create file certifications from local documents,
- upload attachments for a True Flow,
- keep both text operations and upload operations in the same MCP client.