3 ms·

We use MCP in production since March 26 for user-facing endurance sports analytics and planning that integrates directly with the MCP host, in this case the cha

We use MCP in production since March 26 for user-facing endurance sports analytics and planning that integrates directly with the MCP host, in this case the chat interfaces of ChatGPT, Claude, Grok, Perplexity.ai, Mistral, you name it. All of those let users add either custom MCP servers, which users can do with a simple explanation. To connect Claude for example: https://www.tredict.com/faq/connect-claude-web-with-tredict/ https://www.tredict.com/faq/connect-claude-web-with-tredict/ This way users can use Claude to create and push workouts with their Garmin devices based on a prior analysis. We also have a ChatGPT App, which uses MCP in the background: https://chatgpt.com/plugins/plugin_asdk_app_69aef5b699a0819184512d57743fc1cd https://chatgpt.com/plugins/plugin_asdk_app_69aef5b699a08191... The point here is, MCP is the backbone behind the product and enables regular users to do things without knowing anything about it. The whole "is MCP useless?" discussion is totally pointless from a regular consumer-user perspective, they even do not know what MCP is sometimes. The Tredict ChatGPT App connects with one click and a simple oauth flow. That's it.

adityapatadia 1mo ago
This. We also thought MCP was useless, but now the workflows by ChatGPT and Claude are so good; it's as good as installing an app from the App Store. We launched MCP for our SaaS and immediately found users using it. API and MCP all are just buzzwords for customers. What they care about is whether they can get tasks done in our SaaS using Claude or ChatGPT. If that happens, it's a success.
- deadbabe 1mo ago
  Do you not expose a standard REST api?
  - edgyquant 1mo ago
    MCP is not just a rest api its a layer on top
    - allknowingfrog 1mo ago
      A layer than honestly doesn't do much, as I understand it. What does MCP as a protocol actually solve? Is it more than a bandwagon?
      - woofcat 1mo ago
        My company uses MCP in production to connect different AI products together that were developed by different teams. It makes the connections very easy, where a REST interface often has quirks and features that you have to understand.
        allknowingfrog 1mo ago
        That's fair. REST isn't much of a standard. MCP can be just as badly designed and documented as REST, but at least there's a standard for authenticating and listing the options. Reading through other top-level comments, this seems to be the theme. MCP usage is mostly driven by ease of connection.
      - KellyCriterion 1mo ago
        Im not deep in there, but Id guess it offers some discovery mechanisms? (not sure if my understanding is correct)
        saalweachter 1mo ago
        Basically it's just bundling the API documentation into a standard format to plug into LLMs, if you're comfortable running prompt injection on yourself and downloading random text from random websites and telling your favorite LLM to use it to access your banking information.
      - bavell 1mo ago
        It's a bit of a nothingburger IMO, but charitably you could think of it as a rest API + bundled agent instructions.
      - 26d ago
  - adityapatadia 1mo ago
    We do. MCP works on top of it. I say MCP is just lightweight layer on top of REST and as long as it works for end users I don’t see any reason not to adopt it.
- openoba 29d ago
  [flagged]
hncringe 1mo ago
[flagged]
flessio 22d ago
We've found the same. Agents are so sophisticated now that we haven't really focused on human users for our MCP and skill. Instead we have an agent page (https://fless.io/ai-agents https://fless.io/ai-agents) explaining where to find our MCP, what it does (finds apartments) and how to use it. Combined with github presence and some other places agents just seem to find and use whatever works for them. This is all largely invisible to end users who just use us through their agents to find apartments. The exception is OpenAI which as you found out doesn't allow MCP for chat users (does for codex) instead requiring an app-store type listing. Not so open and triggers an app store style discovery process (and presumably tax in the near future).

adityapatadia 1mo ago

This. We also thought MCP was useless, but now the workflows by ChatGPT and Claude are so good; it's as good as installing an app from the App Store. We launched MCP for our SaaS and immediately found users using it. API and MCP all are just buzzwords for customers. What they care about is whether they can get tasks done in our SaaS using Claude or ChatGPT. If that happens, it's a success.

deadbabe 1mo ago
Do you not expose a standard REST api?
- edgyquant 1mo ago
  MCP is not just a rest api its a layer on top
  - allknowingfrog 1mo ago
    A layer than honestly doesn't do much, as I understand it. What does MCP as a protocol actually solve? Is it more than a bandwagon?
    - woofcat 1mo ago
      My company uses MCP in production to connect different AI products together that were developed by different teams. It makes the connections very easy, where a REST interface often has quirks and features that you have to understand.
      - allknowingfrog 1mo ago
        That's fair. REST isn't much of a standard. MCP can be just as badly designed and documented as REST, but at least there's a standard for authenticating and listing the options. Reading through other top-level comments, this seems to be the theme. MCP usage is mostly driven by ease of connection.
    - KellyCriterion 1mo ago
      Im not deep in there, but Id guess it offers some discovery mechanisms? (not sure if my understanding is correct)
      - saalweachter 1mo ago
        Basically it's just bundling the API documentation into a standard format to plug into LLMs, if you're comfortable running prompt injection on yourself and downloading random text from random websites and telling your favorite LLM to use it to access your banking information.
    - bavell 1mo ago
      It's a bit of a nothingburger IMO, but charitably you could think of it as a rest API + bundled agent instructions.
    - 26d ago
- adityapatadia 1mo ago
  We do. MCP works on top of it. I say MCP is just lightweight layer on top of REST and as long as it works for end users I don’t see any reason not to adopt it.
openoba 29d ago
[flagged]

hncringe 1mo ago

[flagged]

flessio 22d ago

We've found the same. Agents are so sophisticated now that we haven't really focused on human users for our MCP and skill. Instead we have an agent page (https://fless.io/ai-agents https://fless.io/ai-agents) explaining where to find our MCP, what it does (finds apartments) and how to use it. Combined with github presence and some other places agents just seem to find and use whatever works for them. This is all largely invisible to end users who just use us through their agents to find apartments. The exception is OpenAI which as you found out doesn't allow MCP for chat users (does for codex) instead requiring an app-store type listing. Not so open and triggers an app store style discovery process (and presumably tax in the near future).