6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Book desks and rooms and draft floor plans in Robin from Claude.
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 Robin MCP server connects Robin's workplace platform to Claude. Employees book, move and cancel desks, attach rooms to meetings and find colleagues in plain language. Workplace teams with planning permissions draft floor-plan changes and stack plans, then publish them. Every action runs as the signed-in user, within that user's Robin role.
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.
initialize and a read of the protected-resource metadata.Usually because your Claude Owner has not added it yet. Robin's help article says that on Claude Team and Enterprise plans an Owner must first add Robin under Organization settings, then Connectors, before members can connect. Share the admin steps with them, or find Robin in the directory and select Request. Each employee then connects with their own Robin account and sign-in.
Because Claude can only see what your own Robin account can see. Robin's troubleshooting guidance is to check that the same floor, desk or person is visible to you in Robin itself. If it is not, ask your Robin administrator about your permissions. Planning tools, such as creating or publishing floor-plan drafts, are hidden entirely from users who lack those permissions.
That depends on your AI client, not on Robin. Robin labels each action as read-only or as changing data using standard MCP annotations, so clients can ask before a change runs. Robin's security article says whether the client actually asks is decided by the platform and its settings. Leave approval on for changes, and remember that a meeting change applies to everyone on it.
Turn off Allow MCP connections under Integrations, then Manage MCP Access. Robin says that stops everyone in the organization from connecting, and existing connections end within an hour, at the next token refresh. With custom roles you can instead remove the AI assistants permission from the Member role and grant it only to approved users through a custom role.
Usually a stale connection. Robin's troubleshooting advice is to remove the connector, add it again and reconnect, so Claude starts a fresh sign-in. If sign-in still fails, check that your organization allows MCP connections and that one of your Robin roles carries the AI assistants permission, because Robin checks both before it shows the consent screen.
https://mcp.robinpowered.com/mcp (2026-11-18): anonymous initialize returned HTTP 401 with WWW-Authenticate: Bearer and a resource_metadata URL. · retrieved 2026-11-18https://mcp.robinpowered.com/.well-known/oauth-protected-resource/mcp (2026-11-18; HTTP 200). Source for the authorization server and the 12 scopes. · retrieved 2026-11-18documentation URL. Source for prerequisites, setup and troubleshooting. · retrieved 2026-11-18docs/marketing/data/anthropic-directory-2026-11-17.json. Source for the partner tier, endpoint, transport, the 46 tool names, the listing date and the description. · retrieved 2026-11-17Connect Robin (Workplace) once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.