Aleph
by Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant. 112 tools, OAuth sign-in, identity scopes only, works in chat and inside Excel.
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.
Connect Aleph via MCP
https://mcp.getaleph.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Aleph Tools & Capabilities (112)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The vendor's documentation covers 14 tools; the directory lists 112. Sizing this connector from Aleph's Available Tools section alone understates its reach by a wide margin. The undocumented remainder includes user management, permission editing, SQL execution and sixteen deletions.
- There is no read-only grant. All four advertised scopes are identity scopes, so the consent screen offers nothing to decline. Scope your access by choosing which Aleph account connects.
- Nothing in the listing undoes a deletion. Recovery exists only for table and dashboard
- An Admin has to enable AI features first. This is a workspace-level toggle under Settings → AI, not a per-user preference, so an individual cannot self-serve a connection.
- We could not read tool schemas or safety annotations. The endpoint requires authentication, so the count and names are the directory's and parameter-level detail is not published here. What we read directly is the auth posture and the advertised scopes.
- The authorization chain runs through a Cloud Run hostname. Not a defect — but it means the consent flow shows a host that does not carry Aleph's branding.
- Aleph publishes no public pricing or plan matrix. Its documentation gates the connector on an active account with AI features enabled rather than on a named tier, so confirm availability with Aleph rather than inferring it.
- Aleph's own guidance is to start read-only. Its MCP guide recommends pre-approving read tools only, piloting with two or three users, and expanding to write-back last. Worth following on a connector with this much write surface.
Frequently asked questions
What do you need before connecting Aleph to Claude?
Three things, per Aleph's MCP configuration page: an active Aleph account, AI features switched on by a workspace Admin under Settings then AI, and an MCP-compatible client. The Admin toggle is the gate people hit first. Aleph's own troubleshooting says that if authorization fails, ask your Admin to enable AI in that settings screen.
Does the Aleph MCP connector see everything in your workspace?
No. It sees what your own login sees. Aleph documents that the connection inherits your user's permissions and is not a shared service account, and that answers respect your existing mappings and permissions. Aleph's security page describes fine-grained controls down to individual data tables and dimensions, which is the model the connector inherits.
Can the Aleph MCP server delete your data?
Yes. Sixteen of the 112 listed tool names begin with delete, covering spreadsheets, dimensions, mappings, folders, dashboard pages, users and user groups. No tool in the listing undoes a deletion. Aleph documents version control that records and restores changes, and two tools restore versions, but a version restore is not the same as an undelete.
Which AI tools work with the Aleph MCP server?
Aleph publishes setup steps for Claude Desktop, Claude.ai, Claude Code, Cursor, VS Code with Copilot and ChatGPT, and states that any MCP-compatible client can connect over HTTP transport. Its announcement adds Lovable and spreadsheet surfaces, describing Aleph MCP working inside Excel and Google Sheets alongside chat.
Why does the Aleph OAuth screen show a Google Cloud Run address?
Because Aleph's authorization metadata is served from a Cloud Run host rather than a getaleph.com subdomain. We read the server's own descriptor on 2026-08-18 and it names server-ruqxzhwjkq-uc.a.run.app as the authorization server. That host in turn points at Aleph's Auth0 tenant, which Aleph's security page names as its identity provider.
Is the Aleph MCP connector read-only?
No, and it cannot be made read-only at the consent screen. The server advertises four scopes and all four are identity scopes: openid, profile, email and offline_access. There is no application-level scope such as data:read to decline, so narrowing what the connector may do happens in Aleph's own permission model, not in the OAuth grant.
Sources
- Aleph MCP Configuration & Support (retrieved 2026-08-18; the directory publishes the apex-domain form, which 301-redirects to this
wwwURL; prerequisites, server URL, per-client setup, Available Tools, example prompts, troubleshooting) · retrieved 2026-08-18 - Aleph MCP product page (retrieved 2026-08-18) · retrieved 2026-08-18
- Aleph, "Aleph MCP: Trusted finance data in Claude, ChatGPT, Excel & more" (retrieved 2026-08-18; supported clients, spreadsheet surfaces, permissions and mappings statement, vendor FAQ) · retrieved 2026-08-18
- Aleph, "MCP for finance teams" (retrieved 2026-08-18; per-user permission inheritance, read-only rollout guidance) · retrieved 2026-08-18
- Aleph, "MCP-compatible FP&A platforms in 2026" (retrieved 2026-08-18) · retrieved 2026-08-18
- Aleph Security & Compliance (retrieved 2026-08-18; Auth0 identity management, permission model, version control) · retrieved 2026-08-18
- Aleph
llms.txtmachine index (retrieved 2026-08-18; 1,602 words, 102 curated URLs).robots.txtallows all paths except paginated integration queries and carries noContent-Signaldirective. · retrieved 2026-08-18 - Live auth posture check against
https://mcp.getaleph.com/mcp— anonymousinitializereturned HTTP 401 withWWW-Authenticate: Bearer resource_metadata=...; the linkedoauth-protected-resourcedescriptor returned HTTP 200 advertisingopenid,profile,emailandoffline_access; theoauth-authorization-serverdocument returned HTTP 200 naminggetaleph.us.auth0.comendpoints (2026-08-18) · retrieved 2026-08-18 - Anthropic Connectors Directory entry (snapshot 2026-08-16) · retrieved 2026-08-16
- Aleph support — · Privacy (apex-domain forms 301-redirect to these)
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- Aleph
- Tools
- 112
- Domain
- mcp.getaleph.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.