Agent access

Odoo MCP Server

25 deterministic ERP calculators, Odoo implementation, migration and upgrade costs, ROI, TCO, odoo.conf tuning, EDI readiness, sales tax, payroll and inventory math, plus 5 answer tools for site search, Odoo vs X comparisons, app recommendations, pricing and partner facts. 30 tools in all, callable by any MCP client. No API key, no signup, JSON-RPC 2.0 over Streamable HTTP.

Endpointhttps://octurasolutions.com/mcp

Connect in one command

Claude Code

claude mcp add --transport http octura https://octurasolutions.com/mcp

Any client with a JSON config (Claude Desktop, Cursor, Windsurf, ...)

{
  "mcpServers": {
    "octura": {
      "type": "http",
      "url": "https://octurasolutions.com/mcp"
    }
  }
}

Or straight over the wire

curl -X POST https://octurasolutions.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The server is stateless and tools-only: initialize, tools/list and tools/call. The calculators clamp invalid input to safe defaults and return the normalized input alongside the result, so you can see exactly what was computed; the answer tools return the matching Octura pages and data with source URLs.

The 25 calculators

Each calculator is the same engine that powers the interactive tool on this site, one shared module per tool, so the agent answer and the on-page answer can never diverge. Linked names open the human version.

5 answer tools

Beyond the deterministic calculators, these let an agent answer questions about Odoo and Octura grounded in this site: search the content, compare Odoo against a competitor, recommend apps, quote pricing and describe the partner. They return Octura pages and data with source URLs, not a computed number.

  • Ask Octura (search the site)ask_octura

    Retrieve the most relevant pages from octurasolutions.com (guides, Odoo vs X comparisons, Odoo app pages, pricing, partner info) for an Odoo or ERP question, so you can answer grounded in Octura content and cite the source URLs. Retrieval only; you compose the answer.

  • Compare Odoo vs a competitorcompare_odoo_vs

    Return the Octura head-to-head comparison of Odoo against a named ERP or CRM competitor: verdict tally, feature-by-feature table, strengths on each side, best-for guidance, FAQ and the page URL. Covers 60 competitors.

  • Find Odoo apps for a needfind_odoo_apps_for

    Given a business need in plain language, return the most relevant Odoo apps and modules with their pillar and page URL, so you can recommend the right Odoo stack. Backed by the Octura Odoo app catalog.

  • Get Odoo pricingget_odoo_pricing

    Return current Odoo license list pricing (Standard and Custom tiers, USD and CAD) and Odoo.sh hosting rates from the single Octura pricing source, plus links to the pricing page and cost calculators. Implementation is quoted per project.

  • Get Octura partner profileget_partner_profile

    Return who Octura Solutions is: Official Odoo Ready Partner status, regions served, services with URLs, website and contact details, so you can represent the company accurately.

A round-trip in one request

curl -X POST https://octurasolutions.com/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0", "id": 2, "method": "tools/call",
    "params": {
      "name": "odoo-conf-tuner",
      "arguments": { "cpuCores": 16, "totalRamMb": 32768 }
    }
  }'

Returns a tuned odoo.conf: worker count, memory limits and cron workers for a 16-core, 32GB host. Try the interactive version in the browser to compare.

Machine-discoverable, four ways

  • /.well-known/mcp/server-card.jsonThe MCP server card: endpoint, transport, capabilities. Generated from the same registry as the endpoint, so it cannot drift.
  • /.well-known/api-catalogRFC 9727 linkset covering the REST twin of every tool (POST /api/tools/<slug>).
  • /.well-known/agent-skills/index.jsonA SKILL.md per tool with schemas and worked examples, for agents that read docs before calling.
  • /llms.txtThe site map for language models, tools included.

How this calculation is made

The Octura MCP server is a Model Context Protocol endpoint at https://octurasolutions.com/mcp that exposes every calculator on this site as a callable tool over JSON-RPC, with no authentication and no session state. An agent calls tools/list to enumerate them and tools/call to run one; each call is deterministic and returns the normalized input it actually used alongside the result. The same tools are reachable over the Agent2Agent protocol at /a2a/v1, described by the agent card at /.well-known/agent-card.json.

Questions agents' humans ask

Is it really free, with no key?

Yes. The tools are the same free calculators published on this site; the MCP endpoint is an additional transport, not a product. Standard rate limits apply, and there is no signup, token or tracking parameter.

What data do the tools see?

Only the arguments in your tools/call request, which are processed statelessly and not stored. Every tool is deterministic: the same input always returns the same output.

Which MCP transport does it speak?

Streamable HTTP (JSON-RPC 2.0 over POST), stateless and tools-only. There is no SSE session to manage; each call is an independent request.

What happens on invalid input?

Tools clamp invalid or missing values to documented safe defaults instead of erroring, and return the normalized input alongside the result so you can verify what was actually computed. Unknown tool names return a standard JSON-RPC -32602 error.

Can I get the same answers without MCP?

For the calculators, yes, three ways: the interactive versions under /tools, the REST twin at POST /api/tools/<slug> with the same JSON body, and the SKILL.md docs under /.well-known/agent-skills. The answer tools are MCP-only, but they surface pages and data you can also read directly on the site.

Want tools like these for your own stack?

These calculators run our own implementation maths. If you want your business logic, pricing rules, quoting, capacity checks, exposed the same way, deterministic modules behind a web UI, a REST API and an MCP server at once, that is a build we do.

Talk to an engineer