3 ms·

> we build own MCP > we use existing models via their API > we use existing tools/services/platforms > ChatGPT/OpenWebUI-like web interface > mostly uses te

> we build own MCP > we use existing models via their API > we use existing tools/services/platforms > ChatGPT/OpenWebUI-like web interface > mostly uses text, no image, no desktop control (?) hardly can see what this app brings. also, it is paid and requests are routed to someone else? shouldn't this be free, local, and with bring-your-own–key already with things like ollama/llama.cpp?

hgaddipa001 1y ago
We actually don't use MCP! We just make our own tools in-house :) Hmm the local open source model is something we've thought of, but currently haven't found open source models to be usable
- AtomicByte 1y ago
  [flagged]
  - hgaddipa001 1y ago
    We don't use open source models as of right now!
  - dang 1y ago
    > Out of all the AI slopups I've seen, y'all might the worst. Have fun, clowns. You can't attack others like this here. We've banned the account. If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html.
- AmazingTurtle 1y ago
  Why __don't__ you use MCP?
  - hgaddipa001 1y ago
    Find that the quality of them currently aren't there yet for a general system. They tend to be designed just to use that singular app instead of to be used in parallel with other apps.
    - esafak 1y ago
      But you are compatible with MCP, right? Otherwise users are going to miss out on the MCP ecosystem. And you are going to be spending all your time developing your own versions of MCP plugins. Wouldn't it be easier to improve the existing ones?
      - hgaddipa001 1y ago
        It's a bit more complicated. We have a full custom single agent architecture, sort of like Manus that isn't fully compatible with MCP
      - tptacek 1y ago
        MCP is what you use to make tools you own compatible with agents (like Claude Code) that you don't --- or vice/versa. It's not doing anything useful in the scenario where you own both the tool calling code and the agent.
        esafak 1y ago
        The question is whether the tools are limited to what they offer.
        tptacek 1y ago
        Are you sure they want to provide access to arbitrary random tools other people wrote? It's easy enough to add MCP support to native tool calls, but I don't know that that's a great idea given their problem domain.
    - bfeynman 1y ago
- brazukadev 1y ago
  [flagged]
  - hgaddipa001 1y ago
    It's useful for quality. For example we can read and attach pdfs to gmail which not a lot of people can, since we have our own internal storage api.
  - brazukadev 1y ago
    oh so now we are flagging people that think not having MCP support is bad?
    - nikolayasdf123 1y ago
      HN is out of control.

hgaddipa001 1y ago

We actually don't use MCP! We just make our own tools in-house :) Hmm the local open source model is something we've thought of, but currently haven't found open source models to be usable

AtomicByte 1y ago
[flagged]
- hgaddipa001 1y ago
  We don't use open source models as of right now!
- dang 1y ago
  > Out of all the AI slopups I've seen, y'all might the worst. Have fun, clowns. You can't attack others like this here. We've banned the account. If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html.
AmazingTurtle 1y ago
Why __don't__ you use MCP?
- hgaddipa001 1y ago
  Find that the quality of them currently aren't there yet for a general system. They tend to be designed just to use that singular app instead of to be used in parallel with other apps.
  - esafak 1y ago
    But you are compatible with MCP, right? Otherwise users are going to miss out on the MCP ecosystem. And you are going to be spending all your time developing your own versions of MCP plugins. Wouldn't it be easier to improve the existing ones?
    - hgaddipa001 1y ago
      It's a bit more complicated. We have a full custom single agent architecture, sort of like Manus that isn't fully compatible with MCP
    - tptacek 1y ago
      MCP is what you use to make tools you own compatible with agents (like Claude Code) that you don't --- or vice/versa. It's not doing anything useful in the scenario where you own both the tool calling code and the agent.
      - esafak 1y ago
        The question is whether the tools are limited to what they offer.
        tptacek 1y ago
        Are you sure they want to provide access to arbitrary random tools other people wrote? It's easy enough to add MCP support to native tool calls, but I don't know that that's a great idea given their problem domain.
  - bfeynman 1y ago
brazukadev 1y ago
[flagged]
- hgaddipa001 1y ago
  It's useful for quality. For example we can read and attach pdfs to gmail which not a lot of people can, since we have our own internal storage api.
- brazukadev 1y ago
  oh so now we are flagging people that think not having MCP support is bad?
  - nikolayasdf123 1y ago
    HN is out of control.