6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search your participant panel, build studies from templates, schedule interviews and act on incentives.
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 Rally MCP server connects a Rally UX research workspace to Claude, Claude Code, Cursor and any MCP-compatible agent. It exposes 67 tools covering studies, participant search, recruiting, screeners, interview scheduling, messaging and incentives — so research teams run recruitment and synthesis in conversation instead of in the Rally app. Rally ships it as Beta.
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.
send_message), cancel their booked interview (cancel_interview) and cancel their incentive (cancel_incentive). An assistant misreading an instruction here has a consequence outside your workspace, and no MCP-level confirmation step exists that we can see — Rally documents approve-before-execute for the in-app Rally Agent during Early Access, and does not extend that statement to the MCP.get_person, get_study_participant, get_raw_transcript and search_study_responses return participant records and verbatim transcripts into the assistant's context. That is the connector working correctly, and it means a chat log becomes a place research PII now lives, subject to your own retention and access rules. Rally's compliance posture covers Rally: it is SOC 2 Type II certified, GDPR, CCPA and HIPAA compliant, and states it never sells data. None of that governs what your AI client stores.mcp:tools is the only application scope the server advertises. There is nothing narrower to approve at consent time, so read-only access is not something the connection can be granted.cancel_interview has no documented inverse.resolve_decision) are consistent with that..well-known descriptors. Everything above about tool behaviour comes from Rally's documentation or the directory listing.Add it as a custom connector. Rally documents the path as Customize, then Connectors, then Add custom connector, entering https://mcp.rallyuxr.com/mcp and clicking Add. Claude opens your browser to sign in to Rally, and the connection is active once you approve access. On Team and Enterprise plans an Owner must add the connector in Organization settings first.
Your OAuth session needs restarting. Rally's troubleshooting tells you to disconnect and reconnect the server in your client to start a new sign-in. A 401 is also what an anonymous request always returns, so the same error appears if the client never completed the browser sign-in step at all.
Tool discovery can lag the connection. Rally's troubleshooting says it may take a moment for your client to discover the available tools after connecting, and suggests sending a message such as ping Rally or search my studies to trigger discovery. The connector ships a ping tool for exactly this purpose.
No. Rally documents that the MCP operates entirely within the permission boundaries of the authenticated Rally user, and that it does not have and cannot obtain access to data the user cannot reach through the Rally platform directly. Data restricted from your Rally account stays restricted through the MCP.
No. Rally states the MCP can only create studies from existing templates. Your organization approves the templates, and Template Controls can lock settings such as incentive amount or interview duration so they cannot be changed when a teammate builds a study through the assistant.
Only inside a seven-day window, and only if unclaimed. Rally documents that incentives follow Tremendous' standard seven-day cancellation window: cancelled funds return to your budget automatically within it, after which the incentive is non-cancellable and the funds are considered spent. An incentive a participant has already claimed cannot be cancelled at all.
From your Rally account settings. Rally documents that OAuth sessions can be revoked there whenever you choose, and that deactivating a user within Rally automatically revokes that user's MCP permissions. Revocation is account-level, so it removes the assistant's access to everything at once rather than tool by tool.
https://mcp.rallyuxr.com/mcp — an anonymous initialize returnshttps://mcp.rallyuxr.com/.well-known/oauth-authorization-server — HTTP 200, advertising PKCE (S256 and plain), a dynamic client registration endpoint at /oauth/register, and a scopes_supported list of openid, offline and offline_access that differs from the protected-resource descriptor's. Our own observation, 2026-08-18. · retrieved 2026-08-18/mcp path, Claude, Claude Code, Cursor and mcp-remote setup, the Owner prerequisite on Team and Enterprise plans, all example prompts and their tool mappings, the template-only study constraint, the quota-tracking boundary, the permission-bound access and revocation statements, and every FAQ answer drawn from its troubleshooting section. · retrieved 2026-08-18robots.txt and llms.txt for help.rallyuxr.com — and (both HTTP 200, retrieved 2026-08-18). The robots.txt is a named-bot whitelist that explicitly allows ClaudeBot, GPTBot, PerplexityBot and CCBot while disallowing unnamed agents, and carries no Content-Signal directive. The host publishes an llms.txt machine index of every help article, which is how the supporting articles above were located. Appending .md to an article URL returns HTML, not Markdown. · retrieved 2026-08-18partner tier, endpoint, transport and categories (from the committed directory snapshot of 2026-08-16, re-read 2026-08-18) · retrieved 2026-08-16Connect Rally once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.