# Connect nanoclaw to LotsTeam

Canonical page: https://lots.team/agents/nanoclaw
Steps checked: 2026-10-01

Ask nanoclaw to turn what users ask for into tasks, draft support replies and publish your changelog in LotsTeam. Add LotsTeam to nanoclaw as a remote MCP server with an API key.

MCP server URL: https://api.lots.team/mcp
REST API docs: https://api.lots.team/docs
Setup instructions for your agent: https://lots.team/skill.md

## What you can do once connected

- Read feedback posts, comment on them, merge duplicates and log new ones, such as a request you heard on a sales call.
- Create and update tasks, assign them to people in your workspace, comment on them and link each one to the posts that asked for it.
- Read support messages and draft replies. A reply goes to the customer only when you say so.
- Draft, update and publish changelog entries, and email the people whose posts asked for the change.
- Set up a project and connect a custom domain to its public portal.

The LotsTeam dashboard runs the same workspace: feedback board, task board, support inbox, changelog and team. Your agent for speed, the dashboard for control, and every change your agent makes shows up there.

## You need

- A current nanoclaw installation with remote HTTP MCP support
- Administrator access to its group configuration and credential gateway
- A LotsTeam API key
- A LotsTeam account. You can create one during sign-in.

## Connect nanoclaw to LotsTeam

1. **Add the server to your agent’s group.** On the host, merge this entry into mcpServers in groups/<group-folder>/container.json. Keep the group’s existing configuration. nanoclaw mounts this file into the agent container at startup.

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

2. **Configure the credential gateway.** Create a LotsTeam API key at https://www.lotstech.com/api. Store it in your installation’s credential gateway, scoped to api.lots.team, and configure the Authorization header as Bearer followed by the key. Allow the agent’s group to use that connection; keep the real key out of container.json.

3. **Start a new agent session.** Restart the affected agent session so it loads the server. Ask nanoclaw “List my LotsTeam organizations and projects” before changing anything.

## What to ask next

- “What did users ask for this week? Group it and open tasks for the top three.”
- “Draft replies to every unanswered support message. I will review before you send.”
- “We shipped dark mode. Write the changelog entry and publish it.”
- “Log this request from my sales call as a post: exports to CSV, asked by Acme.”

## Questions and troubleshooting

### How do I connect nanoclaw to LotsTeam?

Follow the nanoclaw setup above to add https://api.lots.team/mcp. Configure your LotsTeam API key using the credential settings shown. Then ask “List my LotsTeam organizations and projects”.

### Is nanoclaw the same installation as OpenClaw?

No. They are separate projects and runtimes. Follow nanoclaw’s group configuration and credential-gateway steps above; OpenClaw has its own MCP setup.

### Do I need an API key to use LotsTeam with nanoclaw?

Yes. Create one at https://www.lotstech.com/api and keep it out of chats, logs and committed files. Where nanoclaw offers sign-in, use that instead.

### What does LotsTeam cost?

Current plans and prices are on https://lots.team/pricing. Your agent’s own plan or usage fees are separate.

### Does my agent act as me in LotsTeam?

Yes. Your agent signs in as you and can only do what your role allows. A viewer can read, and a member works in the projects they can open.

### Will my agent reply to customers on its own?

Your agent drafts the reply and shows it to you. A reply is emailed to the customer only when you tell it to send.

### What stays in the dashboard?

Deleting a project, the widget and billing stay in the dashboard, and an agent cannot transfer ownership of your workspace.

### The server is configured but requests are blocked

Check your credential gateway’s connection, group grant and network policy for api.lots.team. The remote MCP entry alone does not authorize network access or supply credentials.

## Sources

- [nanoclaw: runner configuration](https://github.com/nanocoai/nanoclaw/blob/main/container/agent-runner/src/config.ts)
- [nanoclaw: credential gateways](https://github.com/nanocoai/nanoclaw/blob/main/docs/gateway-seam.md)