Amazon Textract MCP Server
Amazon Textract is a machine learning service from Amazon Web Services (AWS) that automatically extracts text, handwriting, and structured data from scanned documents.
Quick Start Summary
The Amazon Textract MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Amazon Textract API through natural language. It exposes 10 API endpoints as callable tools, such as AnalyzeDocument, AnalyzeExpense, AnalyzeID, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/amazonaws-com-textract. This integration is sourced from the auto Amazon Textract OpenAPI specification (v2018-06-27) and has a quality score of 46/99 (fair documentation coverage).
Server Details
- Category
- Productivity
- Authentication
- None
- Endpoints
- 10 operations
- Transport
- STDIO
- Spec Version
- v2018-06-27
- Install Command
npx -y @mcp/amazonaws-com-textract
Environment Variables
AMAZON_TEXTRACT_API_KEYExample: your_amazon_textract_api_key
Top Endpoints
/#X-Amz-Target=Textract.AnalyzeDocumentAnalyzeDocument
/#X-Amz-Target=Textract.AnalyzeExpenseAnalyzeExpense
/#X-Amz-Target=Textract.AnalyzeIDAnalyzeID
/#X-Amz-Target=Textract.DetectDocumentTextDetectDocumentText
/#X-Amz-Target=Textract.GetDocumentAnalysisGetDocumentAnalysis
One-Click Install
Copy the snippet for your MCP client and paste it in — zero editing required.
Claude Desktop
Add to claude_desktop_config.json
{
"mcpServers": {
"amazonaws-com-textract": {
"command": "npx",
"args": [
"-y",
"@mcp/amazonaws-com-textract"
],
"env": {
"AMAZON_TEXTRACT_API_KEY": "your_amazon_textract_api_key"
}
}
}
}Cursor
Settings → MCP Servers → Add
{
"mcpServers": {
"amazonaws-com-textract": {
"url": "https://mcpbridge.org/config/amazonaws-com-textract.json"
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code
Use with MCP extension
{
"mcpServers": {
"amazonaws-com-textract": {
"url": "https://mcpbridge.org/config/amazonaws-com-textract.json"
}
}
}Endpoints Explorer
Search and browse the 10 operations supported by this server.
Multi-Language Code Examples
Executable code snippets for calling Amazon Textract endpoints in curl, TypeScript, or Python.
curl -X POST "https://api.apis.guru/v2/specs/amazonaws.com/textract/2018-06-27/#X-Amz-Target=Textract.AnalyzeDocument" \ -H "Content-Type: application/json" \ # No auth required
Manual Configuration
Directly add this block to your JSON config file, or use the hosted config registry URL.
{
"mcpServers": {
"amazonaws-com-textract": {
"command": "npx",
"args": ["-y","@mcp/amazonaws-com-textract"],
"env": {
"AMAZON_TEXTRACT_API_KEY": "your_amazon_textract_api_key"
}
}
}
}Authentication Details
No authentication required. This MCP server runs out-of-the-box.
Documentation Links
Error Handling & HTTP Status Code Matrix
Common status codes, error causes, and resolution steps when invoking Amazon Textract endpoints.
400 Bad RequestCause: Malformed payload parameters or missing required fields.
Resolution: Verify request schema in Endpoints tab before calling tool.
401 UnauthorizedCause: Missing or invalid API key credentials.
Resolution: Set environment variable in MCP client config under env object.
403 ForbiddenCause: Insufficient scope permissions for requested resource.
Resolution: Verify key permissions in developer dashboard.
404 Not FoundCause: Resource URL path or requested entity ID does not exist.
Resolution: Check path variables and parameters.
429 Rate Limit ExceededCause: API rate limit quota exceeded.
Resolution: Implement exponential backoff retry in tool call.
500 Internal ErrorCause: Upstream server runtime fault.
Resolution: Inspect STDIO stderr output for log trace.
Quality Score
Checked against our protocol-compliance rules.
Specification Version: v2018-06-27
Page compiled on: June 13, 2026
Own this API?
Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.
Option 1: Free Verification
Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.
- • Verified badge on page
- • Standard search sorting
- • 2-3 business days review
Option 2: Featured Upgrade($9/mo)
Instant verification plus premium styling, featured badges, and directory placement boost.
- • ★ Featured star & amber highlight border
- • Top of directory search placement
- • Instant activation via claim token
📖 Detailed MCP Integration Guide
A technical breakdown of capabilities, agent workflows, and security/configuration best practices.
textract:AnalyzeDocument) and restricting resource access to only the necessary S3 buckets. All communication should occur over encrypted channels (HTTPS), and document access should be governed by strict S3 bucket policies. Sensitive or personal data extracted from documents should be handled in compliance with data governance policies, potentially using temporary data stores and ensuring it is not logged inadvertently. Configuring the MCP server to use these scoped credentials ensures that the AI assistant operates within a secure and auditable framework.Similar APIs
Other APIs in the Productivity category.
Notion API
Create and manage Notion pages, databases, and blocks through your AI agent.
OAuth2Linear API
Manage issues, projects, and workflows in Linear through your AI agent.
API KeyPlatform API
The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.
Control API v1
The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.
Related MCP Server Integrations
Notion API MCP Setup
Create and manage Notion pages, databases, and blocks through your AI agent.
Linear API MCP Setup
Manage issues, projects, and workflows in Linear through your AI agent.
Platform API MCP Setup
The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.
Control API v1 MCP Setup
The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.
Adyen Test Cards API MCP Setup
The Adyen Test Cards API, provided by the global payment platform Adyen, is a specialized utility designed to streamline the payment integration development and testing lifecycle. Its core capability is the programmatic generation of custom test card numbers, a critical requirement for developers and QA engineers building and validating payment flows in sandbox or test environments. By exposing a dedicated endpoint, `POST /createTestCardRanges`, the API eliminates the manual process of sourcing static test card numbers from documentation or community lists. This is particularly valuable for enterprise-scale applications where testing must cover a complex matrix of scenarios, including various card schemes (Visa, Mastercard, etc.), card types (credit, debit, prepaid), issuer countries, and specific transaction outcomes like approvals, declines, and 3D Secure challenges. Typical use cases span from automated continuous integration (CI) pipelines that require unique test data for each run, to teams developing payment interfaces that must simulate a wide array of real-world customer payment methods.