Product update

Aiso is now available in Claude's connector directory

Connect Claude directly to your Aiso account and work with your AI visibility data in the same conversation where you plan, investigate, and write.

Ben Tannenbaum, Founder of Aiso
By Ben Tannenbaum · Founder, Aiso · LinkedIn
Updated 4 August 2026 · 6 min read · Reviewed by the Aiso Research Team

Bottom line

Aiso's hosted Model Context Protocol server is now listed in Claude's connector directory. The listing exposes 19 tools developed by AISO Boost Ltd. They cover projects, prompts, competitors, visibility reports, citations, URLs, and fan-out analysis. Connecting through Claude's directory needs no local MCP installation.

19
MCP tools shown in Claude's directory listing
1
hosted endpoint operated by Aiso
0
local packages needed through the directory

Source and scope: direct review of the Aiso listing in Claude's connector directory on 4 August 2026, plus Aiso's hosted MCP documentation. The directory labels the listing Community, not verified. Tool access depends on your Aiso account, project setup, and available analysis data.

The useful change is not another dashboard

AI visibility work usually crosses several surfaces. You spot a movement in a report, open the prompts behind it, inspect the sources, compare competitors, and turn the finding into a decision. Each handoff loses context.

MCP gives Claude a structured way to ask Aiso for that data. Claude does not need a pasted screenshot or an exported spreadsheet. It can call the relevant Aiso tool, use the result in its reasoning, and move from finding to explanation in one conversation.

This does not replace the Aiso dashboard. The dashboard remains the clearest place to explore trends and verify the underlying records. The connector makes those records usable inside the work that follows.

Three workflows to try first

Explain a visibility change

Compare my latest visibility snapshot with the previous one. Tell me which competitors gained ground and which cited domains or URLs explain the change.

Audit the prompts you track

Group my tracked prompts by topic and buying stage. Find important gaps, then suggest additions without saving changes.

Find the sources shaping an answer

Show the domains and URLs cited for prompts where competitors appear but my brand does not. Rank the opportunities by how often each source appears.

Ask Claude to show its source records and avoid saving suggested prompt changes until you have reviewed them.

What the 19 tools cover

WorkflowToolsCount
Account and projectsget_access, list_projects, get_project, create_project, update_project5
Prompts and topicslist_prompts, add_prompts, update_prompts, manage_topic, suggest_topics, suggest_prompts, generate_topic_prompts7
Visibility and sourceslist_brands, list_snapshots, brand_visibility_report, domain_report, url_report, get_fanout_metrics, get_fanouts_context7

The three groups contain 5 + 7 + 7 tools, for 19 in total. The names match the Claude directory listing reviewed on 4 August 2026.

Connect Aiso to Claude

  1. 1

    Open the Aiso connector listing

    Use the official directory page and select Connect.

  2. 2

    Authorize your Aiso account

    Follow Claude's authorization prompts. Review the access request before approving it.

  3. 3

    Start with a read-only question

    Ask Claude to list your projects or summarize a visibility report before using tools that change project or prompt settings.

What official means here

This is Aiso's official connector. The Claude listing names AISO Boost Ltd. as the developer and points to Aiso's hosted endpoint at https://app.getaiso.com/api/v1/mcp.

Claude currently places the listing in its Community tier. Claude says Community connectors receive automated reviews but may not meet the quality tier of verified connectors. That label describes Claude's directory status. It does not change who develops or operates the Aiso connector.

If you use another MCP client

The same hosted MCP works with Cursor, Claude Desktop, and other MCP hosts. Create an API key in the Aiso app, point your client to the hosted endpoint, and use a project ID when a tool needs project-scoped data.

Read the Aiso MCP setup and tool reference for headers, client configuration, access rules, and error meanings. Keep API keys out of prompts, screenshots, and shared configuration files.