In-depth architectural comparison of the Amazon Seller MCP and Teamwork MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Amazon Seller MCP
Workplace & Productivity · Local stdio
Quality: 52/100 (Good) | Auth: OAuth 2.0
Teamwork MCP
Workplace & Productivity · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Verdict Summary: Choose Amazon Seller MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Teamwork MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Amazon Seller MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: AMAZON_REFRESH_TOKEN, AMAZON_LWA_APP_ID, AMAZON_LWA_CLIENT_SECRET, AMAZON_AWS_ACCESS_KEY, AMAZON_AWS_SECRET_KEY, AMAZON_ROLE_ARN, AMAZON_MARKETPLACE_ID.
Amazon Seller MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Teamwork MCP belongs to Workplace & Productivity using local stdio subprocess. Select Amazon Seller MCP when you need capabilities focused on workplace & productivity and Teamwork MCP when you require tools for workplace & productivity.
Primary tools included: HTTP and STDIO transport interfaces, Bearer token and OAuth2 authentication, Extensible toolset architecture for Teamwork.com operations.