Atwork

so.atworkPublished by atwork.soOfficial publisherv1.0.1Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote Atwork MCP endpoint that lets an assistant work with your Atwork sheets, tasks, pages and dashboards from Claude, ChatGPT or any MCP client.

What you can do
  • Work with Atwork sheets, tasks, pages and dashboards from the assistant.
  • The manifest lists no individual tools, so the exact operations are not documented here.
  • Access is through a hosted remote endpoint rather than a local package.
When to use it
Worth adding when your team keeps work in Atwork and you want an assistant to reach those sheets, tasks, pages and dashboards without leaving the chat client.
Requirements
A remote MCP endpoint at mcp.atwork.so over streamable HTTP, plus an Atwork account signed in through OAuth. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to your Atwork workspace, which may include team sheets, tasks and dashboards; review the scopes requested at sign-in. The manifest lists no tools, so what the assistant can read or change is not documented in advance.

Installation

In SourceWeft

  1. Open Atwork in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/so.atwork%2Fworkspace/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "atwork": {
      "type": "http",
      "url": "https://mcp.atwork.so/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.