docs: add SDK feature parity matrix#436
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4bfa5b0 to
2692987
Compare
Adds a high-level feature comparison page at /sdk/features covering payment methods, intents, transports, framework integrations, Tempo features, proxy services, and extras across mppx, mpp-rs, and pympp.
2692987 to
efe9169
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4bfa5b0bf0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | Role | TypeScript | Rust | Python | | ||
| |---|---|---|---| | ||
| | **Client** | fetch | reqwest | httpx | | ||
| | **Server** | Elysia, Express, Hono, Next.js | Axum, Tower | Decorator (`@server.pay`) | |
There was a problem hiding this comment.
Replace the nonexistent Python HTTP integration entry
The Python HTTP server cell points readers to @server.pay, but a repo-wide rg 'server\.pay' in this docs tree finds no such API, and the existing Python server reference still documents Mpp.create(...) plus @requires_payment (src/pages/sdk/python/server.mdx:295-316). Because this page is the top-level parity matrix, advertising a Python integration path that users cannot actually find is materially misleading.
Useful? React with 👍 / 👎.
| | **Client** | MCP SDK transport | ❌ | ❌ | | ||
| | **Server** | MCP SDK transport | ❌ | FastMCP (`@pay` decorator) | |
There was a problem hiding this comment.
Mark Rust MCP support as available
These Rust ❌ cells make the parity table inaccurate for readers evaluating MCP support. The upstream mpp-rs repo already ships src/mcp.rs with server helpers like extract_credential/payment_required_error/attach_receipt and client helpers like is_payment_required/extract_challenges/attach_credential, and the module docs explicitly say it works with any MCP SDK. Leaving Rust as unsupported here will steer users away from an SDK capability that already exists.
Useful? React with 👍 / 👎.
| | Role | TypeScript | Rust | Python | | ||
| |---|---|---|---| | ||
| | **Client** | MCP SDK transport | ❌ | ❌ | | ||
| | **Server** | MCP SDK transport | ❌ | FastMCP (`@pay` decorator) | |
There was a problem hiding this comment.
Remove the nonexistent Python FastMCP entry
The Python MCP server cell currently says FastMCP (@pay decorator), but the current upstream pympp MCP example (examples/mcp-server/server_decorator.py) uses the MCP Python SDK plus Starlette with mpp.extensions.mcp.verify_or_challenge; this docs repo also has no FastMCP or @pay reference under src/pages/sdk/python. As written, the matrix sends Python users toward an integration style they cannot actually use.
Useful? React with 👍 / 👎.
Removed specific payment method examples from the text.
Adds a high-level feature comparison page at
/sdk/featurestracking parity across mppx, mpp-rs, and pympp.Covers:
Inspired by x402's SDK features page.