mcpbeat Sign in

Atwork MCP Server

answering

Atwork is answering right now. Last checked moments ago.

Connect Claude, ChatGPT or any MCP client to your Atwork sheets, tasks, pages and dashboards.

Uptime history 6 days of history · worst day 99%
6 days agonow
98.9%
Uptime 24h
91 of 92 checks
—
Tools
hidden behind auth
367 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Atwork missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of 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 0 min ago.

run in your terminal
claude mcp add workspace --transport http https://mcp.atwork.so/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.atwork.so/mcp
~/.codex/config.toml
[mcp_servers.workspace]
url = "https://mcp.atwork.so/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "workspace": {
      "url": "https://mcp.atwork.so/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "workspace": {
      "type": "http",
      "url": "https://mcp.atwork.so/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.atwork.so/mcp streamable-http sign-in 104 ms 0 min ago

Alternatives to Atwork

same job, measured the same way
Nevent MCP
by nevent-dev

Talk to your live-events CRM (campaigns, analytics, paid ads, segments) in Claude and ChatGPT.

33 installs/wk 59 tools answering
Sesame
by qiwei66

Search and open dashboards, reports, decks and PRs that Claude Code and Codex made on your Mac.

local only
Kireo
by wang1051992187

Long-term memory for Claude Code, Cursor and any MCP client, with a searchable web dashboard.

32 installs/wk local only
Redash MCP
by seob717

Connect Redash to Claude -- query data, manage dashboards, and run SQL with natural language.

473 installs/wk local only
Timequip
by timequip

Manage Timequip projects, tasks, comments, members, and dashboards through MCP.

answering
Dvt
by dvt

Dashboards as data. Author, validate, render, and share dvt dashboards from any MCP client.

answering
i40Pilot
by digitalfactoryfr

Manufacturing BI from your AI client: dashboards, OEE, spreadsheets, scheduling, text-to-CAD.

answering
Showboard
by rohanbeingsocial

Your coding agent answers with dashboards: charts and tables from read-only SQL, Excel and CSV.

778 installs/wk local only

Atwork — questions

Answers built from our own checks of this server.

Why is there no tool list for Atwork?
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 Atwork working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 367 ms. The bar chart above shows every period we have measured.
How do I connect Atwork?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Atwork?
No API key is involved. Atwork 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 Atwork?
It answers our handshake in 367 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.