MCP Server Setup Guide for Axanta

This guide explains how to connect Claude and Codex with Axanta MCP in a simple, step-by-step way.

It is written for administrators and implementation users who need a practical setup without technical confusion.

1. Before You Start

Please make sure the following items are ready before starting the connection setup.

• MCP Server module is installed in Axanta
• MCP Server OAuth module is installed if you want to connect Claude
• You have administrator rights in Axanta
• You have a public MCP URL such as https://your-domain.com/mcp
• Your user belongs to MCP User or MCP Administrator

2. Install and Enable MCP in Axanta

Step 1: Install the required modules

1. Open Apps.
2. Search for MCP Server.
3. Install mcp_server.
4. If you want to connect Claude with OAuth, also install mcp_server_oauth.

Step 2: Enable the MCP endpoint

1. Open Settings.
2. Open the MCP Server section.
3. Enable MCP Server.
4. Set default values such as:
   • Rate Limit
   • Max Records Per Request
   • Session TTL
5. Save the settings.

3. Give MCP Access to the User

Step 1: Assign the MCP security group

1. Open the user who will use Claude or Codex.
2. Assign one of these groups:
   • MCP User
   • MCP Administrator
3. Save the user.

4. Generate an MCP Key

1. Open the required user.
2. Go to the MCP tab.
3. Click Generate MCP Key.
4. Enter the key name.
5. Select the scope:
   • Read Only if the user should only analyze data
   • Enable Write Tools if the user should be allowed to create or update through MCP
6. Enter the rate limit if needed.
7. Click Generate.
8. Copy the generated key immediately.

5. Configure MCP Model Policies

Model policies control what the AI can do with each model. This is one of the most important security layers.

1. Open Model Policies.
2. Create a policy for each business model you want to expose.
3. Enable only the operations you want:
   • Read
   • Create
   • Write
   • Delete
   • Method Call
   • Export
   • Report
4. Save the policy.

6. Add Global Assistant Instructions

Global Assistant Instructions help the AI choose the correct reporting model and use the correct Axanta naming.

Recommended example:

This system must always be referred to as Axanta, not Odoo, in user-facing responses.

For analytical questions, prefer the designated reporting models instead of raw operational models whenever possible:
- Sales data: use report.sales.analysis
- Retail sales data: use report.retail.sales.analysis
- Financial data: use report.account.entries.analysis
- On-hand inventory: use report.stock.onhand
- Stock movement: use stock.movement

Use stock.movement carefully because it may contain large volumes of data. Always narrow queries with filters such as date range, product, warehouse, company, or record limits before reading large result sets.

7. Setup for Claude

Step 1: Create the OAuth client in Axanta

1. Create a new OAuth client.
2. Enter the client name, for example Claude.
3. Enable the client.
4. Enable:
   • Allow Read Scope
   • Allow Write Scope if required
5. In Redirect URIs, enter:
   https://claude.ai/api/mcp/auth_callback
6. Click Generate Credentials.
7. Copy the full Client ID.
8. Copy the full Client Secret.

Step 2: Add the custom connector in Claude

1. Open Claude connector setup.
2. Enter a connector name, for example Axanta MCP.
3. In Remote MCP server URL, enter:
   https://your-domain.com/mcp
4. In OAuth Client ID, paste the value from Axanta.
5. In OAuth Client Secret, paste the actual generated secret.
6. Save the connector.
7. Start authorization and log in with the Axanta user who should use the connection.

8. Setup for Codex

Step 1: Open MCP server settings in Codex

Codex MCP server setup using the Axanta MCP URL and Authorization header.

Step 2: Configure the MCP connection

1. Open MCP Servers in Codex settings.
2. Create or update the Axanta MCP server entry.
3. In URL, enter:
   https://your-domain.com/mcp
4. Under Headers, add:
   • Key: Authorization
   • Value: Bearer YOUR_MCP_KEY
5. Click Save.

9. Claude vs Codex Setup Difference

10. Security Summary

MCP access is controlled by all of the following:

• Axanta user access rights
• MCP security group
• MCP key scope
• MCP model policy

Even if a user is an administrator, MCP model policies can still restrict what is allowed through the AI connection.

11. Troubleshooting

Claude authorizes, but still shows an error

• Check the Axanta log after OAuth token success
• Look for errors on /mcp, initialize, or tools/list
• Reconnect the Claude connector after upgrading the module

Codex cannot connect

• Check that the URL is correct
• Check that the Authorization header is exactly:
  Bearer YOUR_MCP_KEY
• Check that the user’s MCP key is active

The AI uses the wrong model for analytics

• Update the Global Assistant Instructions
• Reconnect the client so it receives fresh instructions
• Make sure the preferred reporting model exists and is readable for that user

12. Final Checklist

• MCP Server is enabled
• User has MCP security group
• User has an active MCP key
• Model policies are configured
• Global Assistant Instructions are saved
• Claude OAuth client is configured correctly if using Claude
• Codex Authorization header is configured correctly if using Codex