Teamwork

ai.b77Published by b77.aiOfficial publisherv1.0.0Updated Oct 24, 2026

AI-first project management: plan epics, assign prioritized tasks, track team time.

The publisher's own server: Teamwork.com

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for AI-first project management: plan epics, assign prioritized tasks and track team time from an assistant.

What you can do
  • Plan and organize epics and project structure
  • Create and assign prioritized tasks
  • Track team time and progress
  • No tool list is published, so exact actions are not documented; capabilities are inferred from the provider's description.
When to use it
Useful when a team already runs project management on this provider's platform and wants an assistant to help break work into epics, prioritize and assign tasks, or review time tracking without switching apps.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no local runtime or package install. Sign-in via OAuth is required. No environment variables or headers are declared.
Before you install
The assistant can likely create and change tasks, assignments and time entries in a shared team workspace, so review before letting it write. Access is granted through OAuth to the provider's hosted service, so project and time data is held by that third party.

Installation

In SourceWeft

  1. Open Teamwork 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/ai.b77%2Fteamwork/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": {
    "teamwork": {
      "type": "http",
      "url": "https://teamwork.b77.ai/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.0LatestSep 16, 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.

Other Teamwork integrations