Lark AgentCore Gateway Interceptor Server vs PayMCP
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Enables Bedrock agents to act as a Lark user, performing document operations (list, create, edit, delete) and identity verification via Lark's REST API, with pe
Comparison
| Feature | Lark AgentCore Gateway Interceptor Server | PayMCP |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 2 |
| Rating | — | — |
| Verified | — | |
| Hosted | Hosted | — |
| Tools | — | — |
| Category | development | development |
| Author | aws-samples | blustAI |
| Repo | aws-samples/sample-lark-identity-on-agentcore-interceptor | blustAI/paymcp |
When to pick Lark AgentCore Gateway Interceptor Server
Enables Bedrock agents to act as a Lark user, performing document operations (list, create, edit, delete) and identity verification via Lark's REST API, with per-user credential injection through a Gateway Interceptor.
When to pick PayMCP
Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)
Looking for something else? Browse all MCPs or check trending this week.