Avaza
com.avazaPublished by avaza.comOfficial publisherv1.1.0Updated Oct 24, 2026
Manage Avaza projects, tasks, timesheets, expenses, invoices, and scheduling from AI assistants.
Overview
Lets an assistant manage Avaza projects, tasks, timesheets, expenses, invoices, and scheduling through a remote OAuth-protected endpoint.
- What you can do
- Connects an AI assistant to an Avaza account so it can work with project and task data. According to the registry description, it covers projects, tasks, timesheets, expenses, invoices, and scheduling. It runs as a hosted remote endpoint rather than a local process, and no individual tool names or schemas are published in the manifest.
- When to use it
- Useful when a team already runs projects and billing in Avaza and wants an assistant to look up or update that work without switching apps. Best suited to project tracking, time and expense entry, invoicing, and scheduling questions handled through chat. Skip it if you do not use Avaza or prefer to keep project and financial data out of an assistant's reach.
- Requirements
- A remote streamable HTTP endpoint at OAuth authentication is required, so an Avaza account and a browser-based sign-in are needed. No environment variables, headers, or local packages are declared. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Avaza in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.avaza%2Favaza-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"avaza": {
"type": "http",
"url": "https://mcp.avaza.com/mcp"
}
}
}Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.