# LotsTeam

> Ship what users ask for. Tell them when it lands. LotsTeam collects feature requests and support messages from your site, turns them into tasks, and publishes what shipped. Run it from ChatGPT, Claude or any MCP-capable agent, or from the dashboard.

- [Agent instructions](https://lots.team/skill.md)
- [Tool reference](https://lots.team/references/TOOLS.md)
- [Workflow reference](https://lots.team/references/WORKFLOWS.md)
- [Pricing](https://lots.team/pricing)
- [REST documentation](https://api.lots.team/docs)
- [Agent API documentation](https://api.lots.team/docs.md)
- MCP: https://api.lots.team/mcp

Pricing: plans cover 3, 10 or 30 projects for $24, $69 or $159 a month (annual is 10x monthly). Extra projects beyond a plan cost that plan's per-project rate (shown on each plan at https://lots.team/pricing); without a plan each project is $9 a month. Both are paid automatically from LotsTech Credits, charged daily. Organizations, team members, posts and tasks are unlimited. Eligible new users get 10,000 free credits valid for 90 days. Purchased credits never expire and work across Lots products.

---

# LotsTeam

LotsTeam is the workspace where a founder and a lean team keep what users ask for, what the team is building, and what just shipped.

You are connected as the person who signed in. You can only do what that person's role allows. A viewer can read. A member can change only their projects.

## Hosting and capacity funding

Use `get_funding_status` for current subscription coverage, credit funding and rates. Subscription coverage is used first; projects beyond it are paid from the owner's credits automatically at the plan's per-project rate ($9 without a plan; plan rates at https://lots.team/pricing), charged daily, with no consent switch: free credits first, then plan credits, then purchased credits. When credits run out, uncovered projects pause until the owner tops up; nothing is deleted. Give the returned `settings_url` when the owner needs to top up or choose a plan. Public pages remain readable when funding ends, but new publishing and paid operations need coverage. Paid AI actions use credits when requested.

## Connect

**MCP endpoint:** `https://api.lots.team/mcp`

Add it as a custom connector (Claude: Customize → Connectors → Add custom connector; ChatGPT: Plugins → Add → Create MCP App, OAuth). The person signs in with the email they use for LotsTeam. No key is pasted into the chat.

Clients that take a config file can use the same URL:

```json
{
  "mcpServers": {
    "lots-team": {
      "type": "http",
      "url": "https://api.lots.team/mcp"
    }
  }
}
```

In Claude Code: `claude mcp add --transport http lots-team https://api.lots.team/mcp`

## What is in the workspace

```
Organization
├── People (roles and project access)
└── Projects
    ├── Posts (requests, bugs, and ideas from the widget and public portal)
    ├── Tasks (the board, with comments)
    ├── Support messages (the inbox, with replies)
    └── Changelog (drafts and published updates)
```

Posts are the user-facing word for what the workspace stores as feedback. Call the post tools. A post's id is `post_id` in tool arguments. A post record's own id is `id`. A task that came from a post carries `post_id`.

The public portal can also show a board of tasks the team chose to share. That board is tasks with the public flag, not a separate planning product.

## What you can do

- Read the organization and its projects.
- List, read, create, and update posts. Comment on a post. Create a post to log a request the person heard outside the widget, such as on a sales call.
- List, create, and update tasks. Comment on a task. Link a post to a task.
- List support threads and reply on one.
- Draft, update, and publish changelog entries.
- List the people in the organization so you can assign a task to a real member.

Creating projects, inviting people, changing roles, branding, domains, the widget, and billing stay in the dashboard. Do not invent tools for those.

## How to work

1. Call `list_organizations`, then `list_projects`, before you write anything.
2. Read the record before you change it.
3. When a person asks you to turn a post into work, create or update the task and call `link_post_to_task`.
4. Before replying to support, call `get_contact_thread`.
5. Show the person a support reply before sending it. `reply_to_contact_message` emails the customer.
6. Publish a changelog only when the person asks you to publish it. If the entry is linked to a task with posts behind it, ask whether to email the people who asked (`notify_requesters`), then say how many were emailed.
7. Assign work only to a user id from `list_organization_members`.
8. If a tool returns a permission error, stop and say which action the account cannot take.

## Reference

- [references/TOOLS.md](references/TOOLS.md) — the 26 tools and their arguments
- [references/WORKFLOWS.md](references/WORKFLOWS.md) — posts, tasks, support, and changelog

---

# references/TOOLS.md

# LotsTeam tools

Agents call these names. The workspace still stores posts in the feedback tables, so a handler result uses `id` on the post itself and `post_id` when a task points at a post.

Pass `project_id` for project work. Get it from `list_projects`. Get `organization_id` from `list_organizations`.

## Workspace

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `list_organizations` | Organizations this account belongs to | — |
| `list_projects` | Projects in an organization | `organization_id` |
| `get_project` | One project | `project_id` |

## Posts

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `list_posts` | Posts from the widget and portal | `project_id` or `organization_id`, optional `status` |
| `get_post` | One post | `post_id` |
| `create_post` | Log a request heard elsewhere (a sales call, an email) | `project_id`, `title` (5+ chars), `description` (10+ chars), `category` (`feature`, `bug`, `improvement`, `question`, `other`), optional `email`, `user_name`, `priority` |
| `update_post` | Change title, description, or status | `post_id`, fields to change |
| `list_post_comments` | Comments on a post | `post_id` |
| `create_post_comment` | Add a comment | `post_id`, `content` |

## Tasks

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `list_tasks` | Tasks on a project | `project_id`, optional `status`, `assignee_id`, `priority` |
| `get_task` | One task | `task_id` |
| `create_task` | Add a task | `project_id`, `title`, optional `description`, `status` (`todo`, `in-progress`, `done`), `priority`, `assignee_id` |
| `update_task` | Change a task | `task_id`, fields to change |
| `list_task_comments` | Comments on a task | `task_id` |
| `create_task_comment` | Add a comment | `task_id`, `content` |

## Links

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `link_post_to_task` | Connect a post to the task that tracks it | `task_id`, `post_id` |
| `list_linked_posts` | Posts linked to a task | `task_id` |

## Changelog

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `list_changelog` | Changelog entries | `project_id` or `organization_id` |
| `get_changelog` | One entry | `changelog_id` |
| `create_changelog` | Draft an entry | `project_id`, `title`, `content` |
| `update_changelog` | Edit a draft | `changelog_id`, fields to change |
| `publish_changelog` | Show it on the public portal; optionally email the people who asked | `changelog_id`, optional `notify_requesters` (emails each author of a post linked to the entry's task, once; ask first). The result's `requesters_notified` says how many were emailed |

## Support

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `list_contact_messages` | Support inbox | `project_id`, optional `status` |
| `get_contact_thread` | The message and every reply | `contact_message_id` |
| `reply_to_contact_message` | Reply and email the sender | `contact_message_id`, `reply_message` |

## Team

| Tool | Purpose | Arguments |
|------|---------|-----------|
| `list_organization_members` | People and roles | `organization_id` |

Use a member's user id as `assignee_id`. Do not invent a teammate.

---

# references/WORKFLOWS.md

# LotsTeam workflows

Start every session with `list_organizations`, then `list_projects`.

## Turn a post into work

1. `list_posts` for the project.
2. `get_post` for the one the person means.
3. `create_task` with a title that says what will change, and `assignee_id` only when they named someone from `list_organization_members`.
4. `link_post_to_task` with that task and `post_id`.
5. `update_post` when the status should change, for example once the work is tracked.

## Move a task

1. `get_task`.
2. `update_task` with the new status or assignee.
3. `create_task_comment` to say what changed, in plain language the team can read.

Status values are `todo`, `in-progress`, and `done`.

## Answer support

1. `list_contact_messages`.
2. `get_contact_thread` before writing.
3. Draft the reply and show it to the person when they asked to review it.
4. `reply_to_contact_message` when they want it sent. The reply is stored on the thread and emailed.

## Publish a changelog

1. Read the tasks or posts that shipped.
2. `create_changelog` as a draft.
3. Read it back with `get_changelog`.
4. `publish_changelog` only after the person asks you to publish.

## What stays in the dashboard

Projects, invites, roles, domains, branding, the widget, and billing are changed by a person in LotsTeam. If they ask for one of those, say it is done from the dashboard and continue with the posts, tasks, support, or changelog work they also asked for.

## Comparisons and buyer guides

- [LotsTeam Pricing Explained](https://blog.lots.team/lotsteam-pricing-explained): Plans, pay as you go and credits, with the per-project rates.
- [LotsTeam vs Featurebase](https://blog.lots.team/lotsteam-vs-featurebase): Per project with unlimited members vs per seat, feedback, support and MCP compared.
- [The Best Feedback Tools With MCP Support](https://blog.lots.team/best-feedback-tools-with-mcp-support): Nine feedback tools compared on plan gate, what the agent can change and price model.
- [Canny Alternatives for People Who Use an AI Agent](https://blog.lots.team/canny-alternatives): Flat-priced options and what Canny costs by tracked users.
- [All comparisons](https://lots.team/compare)
<!-- /compare -->