Claude.ai Integration

Wren AI is available as a connector in Claude's connector directory - claude.ai/directory/wren-ai. Instead of pasting an MCP endpoint URL by hand, you can find Wren AI in the directory inside Claude and connect in a few clicks - then ask questions about your data warehouse directly in a Claude conversation.

Plan support

The Claude.ai connector runs on the same organization-level MCP endpoint as Wren AI MCP, so it requires the Enterprise Cloud plan and above, and an org admin must enable MCP first.

Agentic Mode not supported

Like Wren AI MCP, the Claude.ai connector runs in Interactive Mode only. Requests from Claude use Interactive Mode even if the connected project has Agentic Mode available.

Overview

Once connected, Claude can reach the exposed projects your account is allowed to see in the connected Wren AI organization. Claude picks a project, reads its schema through the semantic layer, and answers in natural language - with SQL and charts generated by Wren AI rather than guessed from raw tables.

• Where: Claude web and desktop apps (Settings → Connectors), or the listing at claude.ai/directory/wren-ai
• Auth: OAuth with your Wren AI account - no API key, no local proxy, no URL to copy
• Security: Row/column-level security is enforced per user, server-side

Before You Begin

1. Wren AI Enterprise Cloud plan and above.

2. An org admin has enabled MCP and exposed projects. In Wren AI, go to Settings → Organization → MCP, turn on Enable MCP for this organization, and toggle Exposed for each project you want reachable from Claude. See Wren AI MCP → Before You Begin for details.

   note

   Only exposed projects are reachable, and each user still only sees projects they're a member of.

3. A Claude account that can add connectors. Connectors are available on the Free, Pro, Max, Team and Enterprise plans - Free accounts are limited to one custom connector.

   On Team and Enterprise plans, an Owner or Primary Owner must enable the connector for the organization first, under Organization settings → Connectors → Browse connectors → Add to your team. Until they do, members can't add it themselves.

   note

   Enabling the connector at the org level doesn't grant anyone data access on its own - each person still signs in with their own Wren AI account, which is what keeps RLS/CLS scoped per user.

Connect Wren AI in Claude

Step 1 - Open the connector directory.

In Claude, go to Settings → Connectors, click Add, and choose Browse connectors.

Step 2 - Search for Wren AI.

Search for WrenAI (or Wren) in the directory and open the Wren AI result.

tip

You can skip straight to the listing at claude.ai/directory/wren-ai.

Step 3 - Connect to Claude.

The listing shows what the connector does and every tool it exposes. Click Connect to Claude.

Step 4 - Log in with your Wren AI account.

Claude redirects you to Wren AI Cloud to authenticate over OAuth. Sign in with your own Wren AI account - data permissions are resolved from whoever logs in here.

That's it - there's no separate authorization screen for the directory connector. When you're returned to Claude, Wren AI shows up in your connectors list as connected and is ready to use.

Using It

Mention the connector in a conversation (for example @wren) or just ask a data question and let Claude pick the tool. Claude discovers your projects with list_projects, reads the schema with get_project_metadata, then answers with ask / generate_sql / run_sql.

Expand Used Wren AI integration to see exactly which tools ran and what was sent - useful when you want to check the question Claude actually asked, or the projectId it chose.

Ask Claude to visualize the result and it renders charts from the same governed query - no copying SQL between tools.

Example prompts:

• "List my Wren AI projects."
• "@wren could you do customer segmentation?"
• "In the Sales project, what were the top 5 products by revenue last quarter? Chart it."

note

The connector is bound to a single Wren AI organization. list_projects returns only the exposed projects in that organization, even if your account belongs to other MCP-enabled organizations.

Tools

Tool	Purpose	Takes projectId
list_projects	Projects you can query	-
get_project_metadata	Table schema for a project	✓
ask	End-to-end natural-language Q&A	✓
generate_sql	Question → SQL	✓
run_sql	Execute SQL	✓
generate_chart	Vega chart spec	✓
generate_summary	Summarize results	✓
respond_clarification	Answer a follow-up question from Wren AI	✓

Data Security

Row/column-level security (RLS/CLS) is enforced per user: policies are resolved server-side from the Wren AI account that authorized the connector, and Claude cannot override them.

Watch out for shared accounts

Anyone connecting with a shared Wren AI account inherits exactly that account's data permissions, so RLS/CLS can't distinguish between the individual people behind it. Have each person connect the connector with their own Wren AI account.

Troubleshooting

Symptom	Likely cause and fix
Searching Wren in Settings → Connectors → Add → Browse connectors returns nothing	On Team/Enterprise, no Owner has added it yet - ask one to add it under Organization settings → Connectors.
The login screen in Step 4 shows the wrong Wren AI account	It reuses your browser's Wren AI session. Disconnect in Settings → Connectors and reconnect as the right account - RLS/CLS follows whoever authorized it.
list_projects returns nothing	MCP is off for the org, no project is Exposed, you're not a member of an exposed project, or you connected a different org.
Fewer rows or columns than the Wren AI web app shows	RLS/CLS of the account that authorized the connector. Compare the same question in Wren AI signed in as that account.
You need a self-hosted or non-default endpoint	The listing points at Wren AI Cloud. Add it as a custom connector instead - see Wren AI MCP.

Related

• Wren AI MCP - the underlying endpoint, plus ChatGPT and Claude Code setup and the custom-connector flow.