Hosted MCP server/Other

LaunchMyStore MCP server

Hosted at api.launchmystore.io·Streamable HTTP

LaunchMyStore exposes a store's products, orders, customers, coupons, analytics, themes, shipping and plans to an agent through 190+ tools. The hosted server speaks both transports: legacy SSE at https://api.launchmystore.io/mcp/sse for Claude Code, Claude Desktop and Cursor, and Streamable HTTP at https://api.launchmystore.io/mcp for Codex and newer SDK clients. Those clients use a pasted Bearer MCP token; claude.ai custom connectors use OAuth. The provider warns that Codex fails against the SSE endpoint.

api.launchmystore.io Streamable HTTP Bearer MCP token Server not checked yet Reviewed 2026-11-16
About

Where it fits

LaunchMyStore merchants who want an assistant to manage store operations and check analytics without the admin UI.

  • Update products, coupons or shipping settings in chat.
  • Review orders and customer records.
  • Check store analytics and theme settings.

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

Connect LaunchMyStore

Claude Code, Claude Desktop and Cursor use the legacy SSE endpoint /mcp/sse. Codex and other newer SDK clients use Streamable HTTP at /mcp. Generate an MCP token in LaunchMyStore; claude.ai custom connectors use OAuth instead.

  1. Generate an MCP token

    Create the token in the LaunchMyStore dashboard. For claude.ai, use its custom connector OAuth flow instead.

  2. Claude Code, Claude Desktop, Cursor

    Use the SSE endpoint with the Authorization header.

    claude mcp add --transport sse launchmystore https://api.launchmystore.io/mcp/sse --header "Authorization: Bearer YOUR_MCP_TOKEN"
  3. Codex and newer SDK clients

    Use the Streamable HTTP endpoint with the same bearer token.

    codex mcp add launchmystore --url https://api.launchmystore.io/mcp --header "Authorization: Bearer YOUR_MCP_TOKEN"

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://api.launchmystore.io/mcp
Host
api.launchmystore.io · /mcp
Transport
Streamable HTTP
Authentication
Bearer MCP token
Server name
launchmystore
Listing type
Community or directory listing

The installer uses the server name launchmystore. 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 launchmystore appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Update products, coupons or shipping settings in chat. 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.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • 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 documentation

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

LaunchMyStore documentationhttps://docs.launchmystore.io/mcp/overview