Avaza

The Avaza MCP Server lets an AI assistant, such as Claude or ChatGPT, work in your Avaza account. You ask in plain English, for example "Log 2 hours on the Marketing Campaign project for today", and the assistant looks things up or makes the change for you. It uses the open Model Context Protocol (MCP) standard.

The server address is https://mcp.avaza.com/mcp.

Before you start

• A paid Avaza plan. Any paid plan can use the MCP Server.
• Your own Avaza login. Each person connects separately, and one person's connection gives nobody else access. The assistant works as you: it sees and changes only what your Avaza roles and project memberships allow.
• A role with API access. Most roles include it. People whose only roles are Customer Finances, Schedule Viewer or Chat User can't connect: Avaza refuses the sign-in. See managing users and contacts.
• An AI tool that supports remote MCP servers with sign-in, such as Claude, ChatGPT, Claude Code, Cursor or VS Code. Its own plan decides whether you can add connectors: Claude's Free plan allows one, on Claude Team and Enterprise an Owner adds it first, and in ChatGPT Business, Enterprise and Edu an admin turns on developer mode.

Connect your AI tool

The Avaza MCP Server setup guide has step-by-step instructions for Claude, ChatGPT, Claude Code, Cursor and VS Code. AI tools change their menus often, so use it if a step below doesn't match what you see.

1. Add Avaza as a custom connector. In Claude, open Customize › Connectors, click + and then Add custom connector. In ChatGPT on the web, turn on developer mode under Settings › Apps › Advanced settings, click Create in Settings › Apps and choose OAuth for authentication. Name it Avaza and paste https://mcp.avaza.com/mcp as the server URL.
2. Sign in to Avaza in the window that opens. Avaza asks whether to grant the app access to your account and lists what it will be able to do. Click Grant Access to Avaza. Your password stays on Avaza's page, and there's no API key to copy.
3. Switch Avaza on in a chat (in Claude and ChatGPT, from the + menu) and try a simple request, such as "Show me my overdue tasks in Avaza".

For Claude Code, run claude mcp add --transport http --scope user avaza https://mcp.avaza.com/mcp, then run /mcp and sign in. In Cursor and VS Code, add the server URL to the tool's mcp.json file. The setup guide has the exact configuration.

What your assistant can do

The MCP Server has 121 tools. Your assistant picks the right ones for each request, so you don't need to know their names.

• Projects and tasks: create and update projects, sections and tasks, add project members, and comment on tasks.
• Time: log and edit time, start and stop timers, submit timesheets, approve or reject them if your role allows, and summarise hours by customer, project, person, task or period.
• Expenses: record, update and submit expenses, and summarise spending by category, merchant or status.
• Billing: see what's ready to bill for each customer, create draft invoices and estimates, add unbilled time and expenses to an invoice, create supplier bills, and record customer and bill payments.
• Scheduling: add and edit bookings and leave, link a booking to a task, and see who is booked when.
• Customers and files: create and update companies and contacts, and attach files to tasks, expenses, estimates and invoices.

The assistant can't send invoices or estimates: it creates drafts, which you check and send in Avaza. It can only edit draft invoices, and it can't delete projects, invoices, companies or contacts.

In AI tools that support interactive apps, some requests open a small Avaza form in the chat, for example to create a task or log time.

Safety and admin controls

• Deletions take two steps. The assistant can delete timesheet entries, expenses, tasks, sections, schedule bookings and leave, webhooks and estimates. It always gets a preview first, and nothing is removed until the deletion is confirmed. A confirmation expires after five minutes. Estimates that have been converted to an invoice can't be deleted.
• Admins can restrict AI access in Settings › Developer Apps & API Access, on the API permissions tab. Account defaults set Read, Create, Update and Delete for each module to Role-based, Admins only or Blocked, and can Limit bulk deletes per user per hour. User overrides tighten the rules for one person, or Block all API access for this user. The rules only ever restrict, never grant more than a person's role, and they also apply to personal access tokens and other connected apps.

The API permissions tab on Account defaults, where Administrators limit what AI assistants and other API connections can do in each area of Avaza: every area is set to Role-based, with the Limit bulk deletes option below the list

• To disconnect, remove Avaza from your AI tool's connector settings. Archiving a person in Avaza also ends their connections.

Your assistant makes real changes in Avaza. Check new drafts before anything goes to a customer.

Troubleshooting

• The sign-in window doesn't open. Allow pop-ups for your AI tool's website, then try again.
• "Could not connect to MCP server." Check that the URL is exactly https://mcp.avaza.com/mcp, with no trailing slash, and that your network can reach mcp.avaza.com.
• Sign-in fails after you log in. Make sure you used the right Avaza login. If Avaza denies access, your roles may not include API access (see above): ask an Administrator.
• The assistant can't find a project or task. Use the exact name from Avaza, and check that your Avaza user can see it. The assistant has the same visibility as you.
• "Blocked by account API policy" or "limit this action to administrators". An Administrator has restricted that action under API permissions. For "Bulk delete rate limit exceeded", try again after the start of the next hour.
• Too many requests. Avaza limits how often apps can call it, and the MCP Server counts as one app for your whole account. Everyone in your account who uses it shares 250 calls a minute and 5,000 a day, and those calls also count towards the account's 1,000 a minute and 20,000 a day, together with your other apps. Minute limits reset at the start of each minute, and daily limits at 00:00 UTC. See API rate limits.
• A tool says it lacks permission, although your role allows it. A connection keeps the permissions granted when you signed in. Remove Avaza in your AI tool and connect again.
• The connection stopped working. The server renews your sign-in automatically, so you normally stay connected. If it stops, for example after your access was removed, connect again and sign in.

For the best results, use exact names, say which dates you mean ("last week", "14 September 2026"), and ask for a preview before bulk changes. You can combine steps: "Log 3 hours on the Marketing Campaign, then show my week's timesheet summary."

Already use Zapier? Zapier MCP is another way to connect an AI assistant to Avaza. For other questions, use the support chat in Avaza or email support@avaza.com.