Astravue
by Astravue
Run an Astravue professional-services workspace from an AI agent — projects, tasks, time entries and timesheets. Anthropic lists 83 tools; Astravue documents 80 and claims 87 and 90 elsewhere. 16 delete tools, identity-only OAuth scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Astravue via MCP
https://api.astravue.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Astravue Tools & Capabilities (83)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Sixteen destructive tools, two of which cascade.
astravue_delete_spaceandastravue_delete_projectare documented as permanently deleting all contained content.astravue_bulk_delete_tasksdeletes many records in one call. Nothing in the listing undoes any of it, and Astravue publishes no restore or trash tool. - OAuth scopes draw no line between read and delete. All five advertised scopes are OpenID identity claims. The only real boundary is Astravue's role model, and for an org Admin that model is unrestricted by design.
- Three directory-listed tools are undocumented by Astravue, including a tag removal that operates across all tasks at once. We could not read their parameters or confirm their behaviour.
- The vendor's tool count is unreliable in both directions. 80 named, 83 in the directory, 87 and 90 claimed. We cannot account for the 7 tools between 83 and 90.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here, and no
readOnlyHintordestructiveHintis reported. - The interactive widget is an unaudited surface. Astravue documents inline editing, status changes and task creation inside the view
astravue_preview_task_listopens. We did not exercise it, and no tool-approval setting governs a click inside a rendered widget. - Whether writes notify colleagues is unresolved. Astravue's comment and notification schemas carry mention and mail fields; the tool documentation publishes no parameters. Treat it as unknown rather than as a no.
- Rate limits are per user per minute, at 100 requests, surfaced as HTTP 429 with a documented 60-second wait. Bulk task creation is capped at 100 per call.
- The server source is not public. Astravue's changelog states the implementation lives in a private codebase, so the repository documents the surface but cannot be read to confirm that any boundary is enforced.
- The RFC 9728 path is a catch-all. Every path under
/.well-known/oauth-protected-resource/returned the identical descriptor on 2026-08-23, including a nonsense control path. The descriptor is nonetheless genuine: the endpoint's ownwww-authenticateheader names that exact URL as itsresource_metadata.
Frequently asked questions
Anthropic's directory lists 83, and that is the number to plan against. Astravue's own documentation disagrees with itself three ways: its README headline says 87 tools, its docs overview table says 90, and both enumerate exactly 80 by name. The 80 named tools are a strict subset of Anthropic's 83, so no listed tool is fabricated.
Three, all tag tools. Anthropic's directory lists astravue_create_tag, astravue_bulk_create_tags and astravue_remove_tag_from_all_tasks, and none appears in Astravue's README table or its supported-tools documentation, both of which show a Tags family of exactly three read-and-attach tools. Two of the three omitted names are writes.
Yes, and it cascades. Astravue's documentation describes astravue_delete_project as permanently deleting a project and all its tasks, and astravue_delete_space as permanently deleting a space and all its contents. Sixteen of the 83 tools carry a delete or remove verb. No tool in the listing restores, un-deletes or reads a trash bin.
Only identity claims, which draw no boundary. The server's RFC 9728 descriptor advertised openid, profile, email, roles and offline_access on 2026-08-23, and every one of those is a standard OpenID Connect scope. None names an Astravue object or verb, so consent cannot grant reading a timesheet without also granting deleting a project.
Billable time and its cost. Astravue is a service delivery assurance platform for professional-services firms, and its timesheet endpoint returns billable and non-billable time plus billable cost per project, member and task. Anthropic's directory lists project financials and time tracking records among the connector's sensitive data types.
Astravue does not document it, and the platform clearly can. Astravue's own comment schema carries a mentionedUserIds array and a viaMail boolean, and its notification schema carries a mentioned flag, so comments generate notifications on this platform. The connector's tool documentation publishes no parameters, so whether astravue_add_task_comment reaches those fields is unresolved.
One hundred requests per user per minute, and 100 tasks per bulk create call. Astravue's README states the server returns HTTP 429 Too Many Requests when the limit is exceeded and advises waiting 60 seconds before retrying. Astravue also states the connector works on all plans including free, so no call spends money or credits.
No. Astravue's README FAQ states the MCP server works on all plans including free. Claude Desktop and Claude.ai do require a Claude Pro, Max, Team or Enterprise plan to add a connector, which Astravue notes in its setup instructions, but that is an Anthropic plan requirement rather than an Astravue one.
No. Astravue's permissions table states that the Guest organisation role is read-only and cannot perform any write operations through MCP. Every tool call runs as your authenticated user with your existing roles, and a call lacking the required role returns HTTP 403 Access Denied rather than silently doing nothing.
Sources
- Astravue MCP supported tools documentation (retrieved 2026-08-23). Reached via the machine index at ;
llms-full.txtreturns 404. · retrieved 2026-08-23 - Astravue MCP overview, server details and total-tools table (retrieved 2026-08-23) · retrieved 2026-08-23
- Astravue MCP authentication and security, token lifecycle and role model (retrieved 2026-08-23) · retrieved 2026-08-23
- Astravue MCP server repository README, tool tables, prompts, resources, rate limits and FAQ (retrieved 2026-08-23).
docs.astravue.com/robots.txtallows all agents and carries no Content-Signal directive. · retrieved 2026-08-23 - Astravue MCP server changelog, private-codebase statement (retrieved 2026-08-23) · retrieved 2026-08-23
- Astravue OpenAPI schemas, comment and notification field definitions — · (retrieved 2026-08-23) · retrieved 2026-08-23
- Astravue global timesheet report endpoint, billable cost fields (retrieved 2026-08-23) · retrieved 2026-08-23
- Astravue product site, service delivery assurance positioning (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: 401 with
www-authenticateathttps://api.astravue.com/mcp, RFC 9728 metadata athttps://api.astravue.com/.well-known/oauth-protected-resource, and authorization server metadata athttps://api.astravue.com/.well-known/oauth-authorization-server(2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Astravue support — <mailto:support@astravue.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Astravue
- Tools
- 83
- Domain
- api.astravue.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.