1. Create _or edit the Claude Desktop configuration file located at: - On macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` -
MCP Bauplan MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Bauplan directly instead of describing what you should do. 1. Create _or edit the Claude Desktop configuration file located at: - On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - On Windows: %APPDATA%/Claude/claude_desktop_config.json.
Once MCP Bauplan is connected, these are the calls the assistant has available:
list_tables — - Lists all the tables in the configured namespaceget_schema — - Get the schema of a data tablesrun_query — - Run a SELECT query on the specified tableSetup — 2. Clone the Repository: bash git clone https://github.com/marcoeg/mcp-bauplan cd mcp-nvdYou will need 4 environment variables: BAUPLAN_API_KEY, BAUPLAN_BRANCH, BAUPLAN_NAMESPACE, BAUPLAN_TIMEOUT. 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.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Bauplan's toolset — list_tables, get_schema, run_query and 1 more — is a fair guide to whether it matches your workflow. It is maintained by marcoeg; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Bauplan's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_tables | - Lists all the tables in the configured namespace |
| get_schema | - Get the schema of a data tables |
| run_query | - Run a SELECT query on the specified table |
| Setup | 2. **Clone the Repository**: bash git clone https://github.com/marcoeg/mcp-bauplan cd mcp-nvd |
{
"mcpServers": {
"mcp-bauplan": {
"command": "/path/to/uvx",
"args": ["mcp-bauplan"],
"env": {
"BAUPLAN_API_KEY": "your-api-key",
"BAUPLAN_BRANCH": "your-branch",
"BAUPLAN_NAMESPACE": "your-namespace",
// Optional
"BAUPLAN_TIMEOUT": "query-timeout-secs" // default 30 seconds
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BAUPLAN_API_KEY | Credential the server authenticates with. | Yes |
| BAUPLAN_BRANCH | Configuration value read at startup. | Optional |
| BAUPLAN_NAMESPACE | Configuration value read at startup. | Optional |
| BAUPLAN_TIMEOUT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.