Hosted MCP server/Development

LystBot MCP server

Hosted at lystbot.com·Streamable HTTP

LystBot lets an agent manage lists for groceries, tasks, and other items across various platforms. The remote MCP server uses OAuth through a six-digit pairing code from Settings -> ChatGPT. Local stdio needs an API key from Settings -> AI Agents, stored with npx lystbot login before running npx lystbot mcp. Without that login step the stdio server returns no usable data.

lystbot.com Streamable HTTP OAuth (six-digit pairing code) remotely; API key for local stdio Server not checked yet Reviewed 2026-11-16
About

Where it fits

Household organizers and productivity teams who need an assistant to manage shared grocery or task lists.

  • Pair a remote client with a six-digit OAuth code.
  • Run npx lystbot login with an API key for local use.
  • Add grocery items to a shared list.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Create an API key under Settings -> AI Agents, log in first, then run npx lystbot mcp. Without the login step the stdio server returns no usable data.

  1. Create an API key

    In LystBot, open Settings -> AI Agents and create an API key.

  2. Log in locally

    Store the key for the local client before starting the server.

    npx lystbot login <YOUR_API_KEY>
  3. Start the stdio server

    Register the command as a local MCP server in your client.

    npx lystbot mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://lystbot.com/api/v1/mcp
Host
lystbot.com · /api/v1/mcp
Transport
Streamable HTTP
Authentication
OAuth (six-digit pairing code) remotely; API key for local stdio
Server name
lystbot
Listing type
Community or directory listing

The installer uses the server name lystbot. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that lystbot appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Pair a remote client with a six-digit OAuth code. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

LystBot repositoryhttps://github.com/touraround/lystbot