LotsTeam

team.lotsPublished by lots.teamOfficial publisherv1.0.0Updated Oct 24, 2026

Turn user requests and support messages into tasks and tell users what shipped, from any AI agent.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

LotsTeam is a remote MCP server that lets an assistant turn user requests and support messages into tasks and report back to users what has shipped.

What you can do
Convert incoming user requests and support messages into tracked tasks from within an AI agent session. Report back to users on what has shipped. Connect over a hosted remote endpoint with OAuth sign-in, without installing a local package.
When to use it
Useful when a team handles user requests or support messages and wants an assistant to capture them as tasks and keep users informed about delivered work.
Requirements
A remote MCP connection to the hosted endpoint at api.lots.team. OAuth authentication is required; no environment variables or headers are declared.
Before you install
The server is hosted by a third party and requires OAuth sign-in, so it receives access tied to your account. It creates tasks and sends updates to users, which changes shared data; review what it writes before relying on it.

Installation

In SourceWeft

  1. Open LotsTeam 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/team.lots%2Flotsteam/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": {
    "lotsteam": {
      "type": "http",
      "url": "https://api.lots.team/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.0LatestOct 13, 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.