Friday Work

com.tryfridayworkPublished by tryfridaywork.comOfficial publisherv0.1.73Updated Oct 24, 2026

Read your Friday profile and sessions, and post into a session as you. Scoped OAuth.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Friday Work is a remote MCP server that lets an assistant read your Friday profile and sessions and post into a session on your behalf, using scoped OAuth.

What you can do
Read your Friday profile and session information through the connected account. Post into a session as you. Access is granted through scoped OAuth rather than shared credentials.
When to use it
Useful if you already work in Friday sessions and want an assistant to pull up your profile and session context or contribute messages to a session without switching apps.
Requirements
A remote MCP endpoint at the provider's hosted address, reachable over the network. A Friday account and completion of the OAuth authorization flow with the scopes the server requests. No packages, environment variables or headers are declared.
Before you install
The server acts as you: posting into a session writes content under your identity, so review what the assistant sends before it is published. OAuth grants access to your Friday profile and sessions; check which scopes you approve and revoke access if no longer needed. Session content is handled by the third-party provider.

Installation

In SourceWeft

  1. Open Friday Work 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/com.tryfridaywork%2Ffriday-work/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": {
    "friday-work": {
      "type": "http",
      "url": "https://www.app.tryfridaywork.com/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. v0.1.73LatestOct 23, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.