Test MCP Server

a quick POC to expose Tableau VDS endpoints through an MCP server and integrate them with Claude Desktop client. Exposed over MCP by the test mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

To run this MCP Server and connect it Claude Desktop follow these steps. These instructions were adapted from the MCP how-to guide. These instructions assume you are using MacOS/Linux. If you're running Windows, refer to the how-to guide linked above.

Configuration

You will need one environment variable: AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by joeconstantino; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Test's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the test mcp server does with a few real requests.