A comprehensive MCP server for Tableau Cloud administration with complete API coverage
Tableau cloud v2 mcp server lets Claude, Cursor and other MCP clients work with Tableau Cloud V2 directly. A comprehensive MCP server for Tableau Cloud administration with complete API coverage.
A comprehensive MCP (Model Context Protocol) server for Tableau Cloud administration built with TypeScript. This server provides enterprise-grade tools with complete Tableau Cloud API coverage, structured logging, and production-ready architecture.
Once connected, the assistant can call these 5 tools directly:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — 1. Copy the environment template: bash cp .env.example .envUsage — The Usage tool exposed by this serverProduction — The server is designed for production deployment with: - Structured logging with configurable levels - Request correlation for debugging - Secure credentialSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
The server reads 4 environment variables: SERVER, PAT_NAME, PAT_VALUE, SITE_NAME. Keep credentials in your client's env block or a secrets manager rather than committing them.
Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. Tableau Cloud V2 sits in that group, and the shape of its toolset — Prerequisites, Installation, Configuration among others — tells you what it is really for. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | 1. Copy the environment template: bash cp .env.example .env |
| Usage | The Usage tool exposed by this server. |
| Production | The server is designed for production deployment with: - Structured logging with configurable levels - Request correlation for debugging - Secure credential handling - Performance monitoring capabilities - Error recovery |
| Variable | Description | Required |
|---|---|---|
| SERVER | Configuration value read at startup. | Optional |
| PAT_NAME | Configuration value read at startup. | Optional |
| PAT_VALUE | Configuration value read at startup. | Optional |
| SITE_NAME | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.