mcpbeat Sign in

Workable MCP Server

answering

Workable is answering right now. Last checked 8 min ago.

Uptime history 47 days of history · worst day 91%
47 days agonow
98.9%
Uptime 24h
90 of 91 checks
Tools
hidden behind auth
396 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Workable does not always answer

Over the last week it answered 97.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.workable.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.workable.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.workable.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.workable.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.workable.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.workable.com/mcp streamable-http sign-in 403 ms 8 min ago

Alternatives to Workable

same job, measured the same way
Workmagic MCP
by workmagicio

WorkMagic MCP

answering
Wordpress Com
by wordpress-com
answering
Audible
by audible
answering
Google Workspace MCP Server
by takiguchi-yu

An MCP server for Google Workspaces.

849 installs/wk local only
Google Workspace MCP
by takiguchi-yu

An MCP server for Google Workspaces.

local only

Workable — questions

Answers built from our own checks of this server.

Why is there no tool list for Workable?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Workable working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 396 ms. The bar chart above shows every period we have measured.
How do I connect Workable?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Workable?
No API key is involved. Workable answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Workable?
It answers our handshake in 396 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.