Adaption
Import, adapt and expand training datasets, then launch AutoScientist fine-tuning runs from an AI agent.
Ask governed business-data questions from Claude under your own row and column security.
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 WisdomAI MCP server lets Claude ask analytical questions of your company's governed data through WisdomAI, which applies its metric definitions, business context and your row- and column-level security. Answers come back as text, tables and charts with the query and definitions behind them. Users with an editing role can also change or delete shared definitions.
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.
mcp:*; your WisdomAI role is the real boundary.Yes, if your admin has enabled it. WisdomAI's FAQ says an access token from your organization's identity provider, such as Entra ID, can replace the standard OAuth sign-in or an API key. That route uses your own instance's MCP URL rather than the shared endpoint, so ask your WisdomAI admin to switch on identity-provider authentication and share the instance URL with you.
Because the endpoint could not recognise the credential as any supported type. WisdomAI's FAQ says the error does not specifically mean the key expired or was revoked. Check three things: the header reads Authorization Bearer followed by the key, the key comes from your instance's API Keys settings, and you send it to your own instance's MCP URL rather than the shared one.
Use an API key. WisdomAI's FAQ says to create one in your API Keys settings and send it as a bearer token to your instance's MCP URL, which needs no interactive OAuth flow. WisdomAI's MCP guide adds that API-key authentication works on every instance-specific URL and cannot be turned off, so treat each key as a full credential for that user.
The hosted server cannot create live apps, build agents or upload files. WisdomAI's FAQ says those tasks stay in the WisdomAI app. It also separates this server from the opposite feature, connecting an external MCP server as a data source inside WisdomAI, which scans metadata and fetches data but is not a general two-way integration. Everything else depends on your WisdomAI role.
POST initialize against https://mcp.wisdom.ai/mcp (2026-11-18): HTTP 401 with WWW-Authenticate naming https://mcp.wisdom.ai/.well-known/oauth-protected-resource and scope mcp:*. The descriptor and the RFC 8414 metadata at https://mcp.wisdom.ai/.well-known/oauth-authorization-server both returned HTTP 200. · retrieved 2026-11-18docs/marketing/data/anthropic-directory-2026-11-17.json. Source for the partner tier, the 2026-08-20 listing date, the endpoint, the 31 tool names and the on-premises statement. · retrieved 2026-11-17Connect WisdomAI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.