Initial MCP Server Setup
Enable the MCP endpoint, set the canonical public URL, choose authentication and data-access modes, and run the first health checks.
Initial setup is completed in Settings > MCP Server. Save after each meaningful change so the endpoint, OAuth metadata, and client configuration are generated from one canonical public origin.
Warning: Use the exact public origin Enter only the origin, such as https://odoo.example.com. Do not enter /mcp, a trailing slash, a database path, or an internal proxy address.
Basic configuration
- Open Settings > MCP Server.
- Enable MCP Server.
- Set Public Server URL to the public HTTPS origin.
- Confirm the read-only MCP URL becomes https://your-domain/mcp.
- Choose an authentication mode. OAuth 2.1 / PKCE is recommended for interactive users. OAuth + Scoped API Keys is recommended when both people and automations will connect.
- Choose MCP Data Access. Restrict With MCP Access Bundles is the recommended production mode.
- Set Maximum Records to a conservative value. The module default is 100 records per standard request.
- Keep Audit Logging enabled.
- Review Allowed Browser Origins and remove origins your deployment does not need.
- Save the settings.
Optional configuration
- Fallback User: required only for Bearer Token or No Authentication mode. OAuth normally runs as the user who approved the connection.
- Rate Limit: leave disabled during initial client setup; OAuth clients can send several discovery requests in a short burst.
- Shared Redis Backend: use for multi-worker or multi-server deployments after installing and testing Redis.
- Instance Notes for AI: document custom fields, business terms, approval rules, module names, and workflow meanings.
First health checks
| URL | Expected use |
|---|---|
| https://your-domain/mcp/docs | Human-readable capability and endpoint page. |
| https://your-domain/mcp/docs.json | Machine-readable documentation summary. |
| https://your-domain/mcp/api/v1/health | Basic enabled and health status. |
| https://your-domain/mcp/api/v1/guide | Instance guide, glossary, and exposed model context after authentication where required. |
| https://your-domain/.well-known/oauth-authorization-server | OAuth server discovery metadata. |
| https://your-domain/.well-known/oauth-protected-resource/mcp | Protected-resource discovery metadata for the MCP endpoint. |
Safe first test
Before connecting ChatGPT or Claude, create one MCP user, one read-only bundle, and expose only a few non-sensitive models such as res.partner or sale.order that the test user can already read in Odoo.
Installation and Requirements
Install the Niyu MCP Server module on Odoo 19, confirm HTTPS and reverse-proxy readiness, and validate the database before configuring clients.
User Roles, Access Bundles, and Model Governance
Assign MCP User or Administrator access, expose exact Odoo models, and restrict permissions, fields, records, result sizes, and tools.