Developer · Remote MCP server
tab
Time tracking for freelancers: start/stop the timer, log hours, see unbilled time and who owes you.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.tabwork/tab- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- app.tabwork
- Namespace
- Namespace verified by the MCP Registry via the domain tabwork.app · how
- Website
- tabwork.app/ai/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.tabwork.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect tab
tab is a remote MCP server: there is nothing to install. Its endpoint is https://app.tabwork.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 developer servers
| Server | Runs |
|---|---|
| sysmcpLive Linux host signal (CPU, memory, processes, network, optional eBPF) for MCP clients. | Local · stdio |
| SyteCheckScan a website for SEO, accessibility, performance and security issues, and read the report. | Local · stdio |
| T1/T2 ProtocolCaller-side T1/T2 heterogeneous validation MCP server. Stdlib-only Python. | Local · stdio |
| T32 MCP ServerTRACE32 debugger MCP - session, dialog, field, history, resource inspection. | Local · stdio |
| TabellumMCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app. | Local · stdio |
| TabfleetLaunch, inspect, control, and share isolated cloud browsers for your agents. | Remote · HTTPLive check: sign-in required |
| Tableau Graphql MCPAsk any Tableau lineage question, in any MCP client, through the Tableau Metadata API. | Local · stdio |
| Tableau Workbook AuditorLocal-only Tableau.twbx audit: lineage, unused fields, duplicate calcs, SQL, version diffs. | Local · stdio |