CEL-powered rules — pricing rules use Common Expression Language for type-safe, auditable conditions.
Pricing Engine MCP Server
Enterprise pricing engine for ADK-Rust Enterprise agents. Provides 26 MCP tools covering the full pricing lifecycle — CEL rule engine, price waterfall, product catalog, customer segments, promotions, quotes/CPQ, market…
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
Price waterfall — deterministic 6-step pipeline: list → segment → promotions → rules → floor/ceiling → tax.
Explain mode — every price calculation can return the full waterfall breakdown showing which rule caused each price movement.
Vertical-agnostic — same engine prices rides, SaaS subscriptions, physical goods, API calls, and professional services.
Audit everything — every rule change, product update, and quote approval is logged immutably.
Zero configuration — starts with no external dependencies. Market intel (FX rates) works immediately via free APIs.
Architecture
How Pricing Engine MCP Server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
MCP client
Discovers schemas, sends calls, and receives typed content.
Pricing Engine MCP Server
Validates the request and owns 21 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
From the project documentation
The server’s published architecture
Tool catalog
What can an agent ask Pricing Engine MCP Server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
21 named tools
price_calculateCalculate price through full waterfall with CEL rules
read onlyrules_validateValidate a CEL expression
read onlycatalog_upsertAdd/update product in catalog
internal writecatalog_getGet product by SKU
read onlycatalog_listList all products
read onlyrules_createCreate pricing rule with CEL condition
internal writerules_listList all pricing rules
read onlyrules_activateActivate a pricing rule
internal writerules_deactivateDeactivate a pricing rule
internal writesegments_createCreate customer segment
internal writesegments_listList customer segments
read onlypromotions_createCreate promotion
internal writeGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
- CEL-powered rules — pricing rules use Common Expression Language for type-safe, auditable conditions.
- Audit everything — every rule change, product update, and quote approval is logged immutably.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
cargo install mcp-pricing{
"mcpServers": {
"pricing": { "command": "mcp-pricing" }
}
}Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in business operations.
Source record
Release and repository metadata for this catalog entry.
- Version
- 2.1.0
- License
- Apache-2.0
- Tools
- 21
- Revision
- f498cf4ffb1c
- Updated
- May 27, 2026