# Claude: approve the crew's work from the chat you already use > For the complete documentation index, see [llms.txt](https://attensira.com/llms.txt). > Every page on this site is also served as Markdown: append `.md` to any URL, or send `Accept: text/markdown`. > Add Attensira to Claude Desktop, claude.ai or the mobile app as a custom connector, sign in, and read, approve and steer SEO work from a conversation. - Canonical page: https://attensira.com/integrations/claude-desktop - Family: integrations - Last updated: 2026-10-05 - Author: Karl-Gustav Kallasmaa (https://x.com/kallasmaa) - Claims as data: https://attensira.com/claims.json?slug=claude-desktop **In short:** Add Attensira to Claude under Settings → Connectors → Add custom connector, with the URL https://mcp.attensira.com/mcp and no authentication fields. Sign in, open a new chat and enable it. Claude can then read your AI visibility, show what the crew has waiting, approve or decline it, and hand the crew new work. Reading is free. ## What it showed on attensira.com (read 2026-10-05) Asked in Claude: "What is waiting on me?" Call: `list_inbox view=triage` 28 items wait on a person: 10 pieces of work to approve and 18 tasks. Three of them: | Row | Value | Note | | --- | --- | --- | | Rewrite a passage on our pricing page | Approve | | | Search Engine Land decides 5 of our losses and is the one we can earn | Task | | | Install the edge SDK so we can see whether AI crawlers reach the site | Task | | _Our own Inbox, where the crew's work waits for our yes._ ## What can Claude do with the crew's work? - Ask what is waiting on you and approve or decline the crew's drafts, pull requests and pitches from the conversation, each marked "via Claude" in the app. - Read mention and citation rates, the prompts you lose, the rivals named instead and the answers themselves, each with its sample size. - Set up Attensira for a new domain from the chat. Claude shows the drafted profile, rivals and goals; payment finishes in your own browser. - Steer a project in plain words, such as "focus on the pricing comparison pages this month", and read the crew's reply later. ## How do I connect Claude? 1. **Add a custom connector** In Claude, go to Settings → Connectors → Add custom connector. Name it Attensira and enter the server URL. Leave every authentication field alone. Attensira publishes standard OAuth discovery, so there is nothing to fill in. 2. **Sign in and approve** Choose Connect and Claude sends you to Attensira to sign in. Approve the access it asks for and you land back in Claude with the connector on. You do not need a workspace first; Claude can set one up for your domain. 3. **Enable it in a new chat** Open a new conversation and turn Attensira on from the tools menu. Existing conversations do not pick up new connectors, which is the usual reason a working connector seems to do nothing. 4. **Check it with get_account** Ask Claude to call get_account. It lists the workspaces the connection reaches, the credit balance, the scopes and the platforms really measured. The connector also works in claude.ai and the Claude mobile apps. ## What stays out of Claude's reach? - Custom connectors depend on your Claude plan. On Team and Enterprise an owner adds the connector first, under Organization settings → Connectors. Attensira cannot lift that. - A signed-in connection always carries read and write: Claude can approve work, add prompts and spend credits if you ask it to. For reads only, use a read-only API key instead. - Approving from Claude is still your approval. Claude changes the approval mode only when you tell it to, it can neither read nor raise your budget, and anything stating a claim still waits for a person. ### What did our own Inbox show? The honest state of a workspace whose founder has not been approving: the crew keeps working, and nothing ships until someone says yes. Most of what waits is not drafts but tasks only a person can do, such as the third row above: installing the edge SDK so the crew can see whether AI crawlers reach the site. One unanswered task can hold up a dozen pieces of finished work, which is why the backlog is worth reading as a list, not one item at a time. ### What is a good weekly habit? Ask Claude two things once a week: what is waiting on you, and what shipped. `list_inbox` with the triage view returns the decisions to take first; `list_deliverables` lists what the crews delivered and where each piece lives. Approving the backlog is the single thing that turns the crew's work into shipped work, and a chat is the least effort way to do it. ## FAQ ### Do I need to fill in a client ID or secret? No. Leave every authentication field alone. Attensira publishes standard OAuth discovery, so Claude finds what it needs by itself. ### I added the connector and my chat shows no tools. Why? Almost always because it is an existing conversation. New connectors are not picked up by conversations that already exist. Open a new chat and enable Attensira from the tools menu. ### Why can I not add a custom connector at all? Custom connectors depend on your Claude plan. On Team and Enterprise, an owner adds the connector first under Organization settings → Connectors. ### Does it work on claude.ai and the mobile app? Yes. The same connector works in claude.ai, Claude Desktop and the Claude mobile apps. ### Can Claude set up Attensira for me? Yes. Ask it to set up Attensira for your domain. It shows what the agents drafted from your site and saves what you keep. Nothing is charged by the assistant; checkout finishes in your browser. ### How do I take access away later? Remove the connector in Claude, or revoke the application under Connections in Attensira. Revoking one client leaves your other connections working. ## Sources Each entry below is one claim on this page. `retrieved` is the date the exporter or a human last saw the source say this, and nothing more: it is not a publication date and not a promise of re-verification. `cite` is the anchor on the canonical page where this claim is rendered. ### claude-new-conversations Attensira's connect documentation states that existing conversations do not pick up new connectors and that a new chat is needed after enabling one. - source: https://docs.attensira.com/mcp/connect (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/claude-desktop#claim-claude-new-conversations > Existing conversations do not pick up new connectors. ### claude-no-auth-fields Attensira's connect documentation instructs Claude users to leave every authentication field alone when adding the custom connector, adding no header and no client ID or secret. - source: https://docs.attensira.com/mcp/connect (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/claude-desktop#claim-claude-no-auth-fields > Leave every authentication field alone — do not add a header, and do not paste a client ID or secret. ### claude-connector-availability Attensira's connect documentation states that custom connector availability depends on the Claude plan and that on Team and Enterprise an owner adds the connector first. - source: https://docs.attensira.com/mcp/connect (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/claude-desktop#claim-claude-connector-availability > Availability of custom connectors depends on your Claude plan. On Team and Enterprise, an owner adds the connector first, under Organization settings → Connectors. ### via-assistant-label Attensira's connect documentation states that anything an assistant files in the workspace is marked with the client it came through, such as via Claude. - source: https://docs.attensira.com/mcp/connect (docs.attensira.com) - retrieved: 2026-10-04 - cite: https://attensira.com/integrations/claude-desktop#claim-via-assistant-label > Anything your assistant files in your workspace (an Inbox row, a change to approve, a question) is marked with the client it came through, such as **via Claude** or **via Cursor**.