Use the TablelistPro MCP server to give AI clients a safe, scoped interface for reading operational data from your organization.
What it does
The MCP server exposes a curated set of tools over an MCP endpoint so an AI client can query TablelistPro data without direct database access.
Current tool coverage is focused on read workflows. Any write or destructive actions should stay behind explicit API ownership and confirmation gates.
Authentication
MCP requests use a bearer token:
Authorization: Bearer <mcp-token>
The token maps to a server-side credential with:
id: credential identifier used for logging and rate limitstoken: bearer token secretorganizationId: organization scope for all callsmanagementToken: upstream management auth token for TablelistPro API callsvenueIds(optional): allowlist of venues this credential can accesslabel(optional): human-readable name for ops/admin use
If the token is invalid or missing, the MCP server returns 401 Unauthorized.
Scope and authorization
Each credential is organization-scoped by default. If venueIds is provided, venue-level tools are constrained to that allowlist.
This means an AI client can only read data the mapped credential is allowed to access:
- wrong organization -> denied
- venue outside allowlist -> denied
- missing required scoped venue id -> request rejected
Use least-privilege credentials and split credentials by environment or use case.
Rate limits
Requests are rate-limited per credential id in a 60-second window.
When exceeded, the MCP server returns 429 Too Many Requests. Clients should retry with backoff and jitter.
Common errors
401 Unauthorized: bearer token missing or invalid429 Too Many Requests: per-credential limit exceeded4xx/5xxupstream API errors: bubbled from TablelistPro API when upstream rejects or fails a request
For production clients, log status code, request id, and tool name for faster triage.
Example MCP client configuration
Use your MCP client's server config and point it to your hosted MCP endpoint:
{
"mcpServers": {
"tablelistpro": {
"url": "https://<your-mcp-host>/mcp",
"headers": {
"Authorization": "Bearer <mcp-token>"
}
}
}
}
Also expose a health endpoint (for example /healthz) in your deployment checks.
Security guidance
- Keep MCP tokens in secret managers, never in source control.
- Rotate tokens on a schedule and immediately after suspected leakage.
- Issue separate credentials per environment (dev/staging/prod).
- Restrict
venueIdswhenever full-organization scope is not required. - Audit MCP access by credential id and request outcome.