6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Run an Astravue workspace from an AI agent: projects, tasks, time entries, timesheets.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Astravue MCP server connects an Astravue workspace — a service delivery assurance platform where professional-services firms run projects alongside billable time and margin — to Claude, ChatGPT and any MCP-compatible agent. Anthropic lists 83 tools spanning spaces, projects, tasks, time entries, custom fields and timesheets. Sign-in is OAuth 2.0 with PKCE.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
astravue_delete_space and astravue_delete_project are documented as permanently deleting all contained content. astravue_bulk_delete_tasks deletes many records in one call. Nothing in the listing undoes any of it, and Astravue publishes no restore or trash tool.readOnlyHint or destructiveHint is reported.astravue_preview_task_list opens. We did not exercise it, and no tool-approval setting governs a click inside a rendered widget./.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 own www-authenticate header names that exact URL as its resource_metadata.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.
llms-full.txt returns 404. · retrieved 2026-08-23docs.astravue.com/robots.txt allows all agents and carries no Content-Signal directive. · retrieved 2026-08-23www-authenticate at https://api.astravue.com/mcp, RFC 9728 metadata at https://api.astravue.com/.well-known/oauth-protected-resource, and authorization server metadata at https://api.astravue.com/.well-known/oauth-authorization-server (2026-08-23) · retrieved 2026-08-23Connect Astravue once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.