Other · Local MCP server
pitwall-mcp
Solo lectura sobre BMW CarData: mantenimiento, neumaticos y bateria de 12V. No afiliado a BMW AG.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sergioprats/pitwall-mcp- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-22
- Updated
- 2026-09-22
- Publisher
- sergioprats (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sergioprats) · how
- Website
- github.com/sergioprats/pitwall-mcp
- Repository
- github.com/sergioprats/pitwall-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | pitwall-mcp | 0.1.1 | stdio |
How to connect pitwall-mcp
pitwall-mcp runs locally from a Python package published to PyPI: pitwall-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx pitwall-mcp. It reads these environment variables: PITWALL_CLIENT_ID (required, secret), PITWALL_VIN (required, secret), PITWALL_CONTAINER_ID (required), PITWALL_TOKEN_FILE, PITWALL_DB_PATH, PITWALL_DAILY_QUOTA and PITWALL_LOG_LEVEL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pitwall-mcp": {
"command": "uvx",
"args": [
"pitwall-mcp"
],
"env": {
"PITWALL_CLIENT_ID": "<secret>",
"PITWALL_VIN": "<secret>",
"PITWALL_CONTAINER_ID": "<value>",
"PITWALL_TOKEN_FILE": "<value>",
"PITWALL_DB_PATH": "<value>",
"PITWALL_DAILY_QUOTA": "<value>",
"PITWALL_LOG_LEVEL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Pipeworx FaqPipeworx FAQ MCP - curated answers to questions ABOUT Pipeworx itself. | Remote · HTTPLive check: ✓ handshake |
| Pīpīwai Trail statusLive Pīpīwai Trail park and road status, compiled from NPS and Hawaii DOT. | Remote · HTTPLive check: ✓ handshake |
| Pir MCPMotion sensor for AI agents: tells when a screen region changes or goes still. Scores, never pixels. | Local · stdio |
| PitbridgeLocal-first MCP bridge for NinjaTrader 8 behind a deterministic guardrail engine. | Local · stdio |
| PixassoEnd-to-end frontend engineering and design orchestrator across 16 foundational pillars. | Local · stdio |
| PixdataOrg CoderideCodeRide eliminates the context reset cycle once and for all. Through MCP integration, it … | Remote · HTTPLive check: ✗ no handshake |
| Pixel SquadsMCP Server for Pixel Squads - observe your AI agents as pixel-art characters in a live office. | Local · stdio |
| PixelcheckReal eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic. | Local · stdio |