Provides a Python SDK to integrate the iwant.fyi demand-side protocol into CrewAI agents, enabling structured purchase intent expression and fulfillment across multiple sources.
Provides a Python SDK to integrate the iwant.fyi demand-side protocol into LangChain agents, enabling structured purchase intent expression and fulfillment across multiple sources.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@iwant.fyi MCP Server I want to buy a used MacBook Pro under $1000"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The iwant.fyi demand-side protocol defines how AI agents express structured purchase intent on behalf of users, receive matched supply across multiple sources, and report outcomes back. It is MCP-native, transport-flexible, and intentionally agnostic about who matches the demand, who fulfills it, and how money moves.
Existing agentic commerce protocols are supply-side: ACP and UCP define how an agent completes a purchase at a merchant; AP2 handles payment authorization; MCP is general tool/data access. None of them defines how an agent expresses what its user wants in a structured, machine-matchable form, or how that demand persists across sessions and gets fulfilled across multiple sources.
The iwant.fyi demand-side protocol fills that gap.
Related MCP server: agent-commerce-mcp-server
v1.1 (Draft) — Current. Additive, backward-compatible with v1.0: signed webhooks for Standing Wants (§16), partial-result transparency (§6.1), retryable error taxonomy (§11.2), idempotency keys (§8.4), capability discovery (§8.2), deterministic ordering + cursor (§6.3).
Read it rendered with anchors at iwant.fyi/protocol/v1.
JSON Schema for the core objects: schemas/1.1/ (also served live at
https://iwant.fyi/.well-known/iwantfyi/schemas/1.1/).
A test kit verifies any implementation against spec §15:
npx @iwantfyi/conformance-kit --mcp https://iwant.fyi/api/mcp --http https://iwant.fyi/api/v1 --api-key <key>Source: conformance-kit/ · npm: @iwantfyi/conformance-kit (Apache-2.0). The
reference implementation also self-reports at /api/v1/conformance.
iwant.fyi — https://iwant.fyi/api/mcp
The iwant.fyi MCP server is the reference implementation. It advertises spec conformance and is the canonical surface to test against.
Framework | Package | Repo |
TypeScript / generic |
| |
LangChain (Python) |
| |
Composio (Python) |
| |
CrewAI (Python) |
|
Three open-source example agents at staugs/iwantfyi-examples.
v1.1 is published as a draft for public comment. Feedback, issues, and proposed extensions are welcome via GitHub issues or directly to hi@iwant.fyi.
The specification is published under the Apache License 2.0. Implementations are not required to be open source.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Demand-side discovery for the agent economy: turn ambiguous intentions into commitments and match th
Agent-native marketplace. Bootstrap, list inventory, search, negotiate, and trade via MCP.
Search and discover advertiser products through an open marketplace for AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/staugs/iwantfyi-spec'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
