Model Context Protocol (MCP)

Altertable's MCP server gives AI clients a governed way to interact with your lakehouse.

Connection Details

Your client must support hosted MCP servers over streamable HTTP and OAuth. Clients that only support local stdio servers cannot connect to Altertable's hosted MCP server.

Connect

1. Add https://mcp.altertable.ai as an MCP server in your client.
2. Start the connection or authorization flow.
3. Sign in to Altertable in the browser when prompted.
4. Choose the organization and environment the client should access.
5. Approve the connection and return to your client.

After approval, the client uses an OAuth bearer token for MCP tool discovery and execution. Access is scoped to the environment selected during authorization.

OAuth Discovery

Compatible clients should discover OAuth settings automatically. Altertable supports protected resource metadata, authorization server discovery, and dynamic client registration.

When a client calls an authenticated MCP method without a valid token, Altertable may return a WWW-Authenticate: Bearer ... challenge that points the client to the protected resource metadata.

Tools And Permissions

MCP tools can list catalogs and semantic models, query the lakehouse, validate SQL, view insights and dashboards, and create outputs such as insights, memories, notifications, and scheduled tasks when write access is approved.

For the exact tool schema, see MCP tools.

Troubleshooting

• Client cannot connect: confirm it supports hosted MCP over streamable HTTP and OAuth.
• Discovery does not start: use exactly https://mcp.altertable.ai.
• Browser sign-in loops: finish authorization in the browser window opened by the client.
• No tools appear: reconnect so the client reruns discovery, authorization, and tool listing.
• Wrong environment: reconnect and choose the correct environment during authorization.