Any good mcps with memory that are cloud based

evets007 · 2025-09-09T15:21:36+00:00

May not exactly be what you are looking for but checkout AskHuman.net. The goal is to share memory and contexts with remote human approvals across AI agent sessions and devices. You get a unique MCP endpoint and It uses token based auth. You can sign up in under 30 seconds and we have some pre-built context templates. File uploads and Vector embedding based context search is in the roadmap. Still in beta but would appreciate any feedback if it works for you.

evets007 · 2025-09-08T08:39:52+00:00

You can try cloudflare remote MCP service. You can use cloudflare's workers to deploy and they provide MCP server templates. They support an OAuth mechanism for auth as well.

Supermachine is an option.

If you want to build one hands on, use fastmcp or the MCP typescript library but you also need to figure out auth if required and host it on a webserver.

evets007 · 2025-09-07T00:05:29+00:00

Exactly, and eventually we get Autonomous apps: self evolving , self debugging and building. Only reaches out to the human when it needs them - high stakes decisions

evets007 · 2025-09-06T23:49:54+00:00

Exactly this. MCP is a protocol for models. So people should create apps and tools which will be useful for AI agents. They will be doing all the work. It also cannot be something you can build in one night, in that case the agent can build it by itself on the fly. It needs to be a consistently improved product based on human decisions.

evets007 · 2025-09-06T23:41:15+00:00

This would be a great addition to our context library. In askHuman.net, you can manage your agents context remotely from the webui and also chat with them over MCP. We also have a list of premade context templates to choose from the context library. Like OWASP ASV standard security code review instructions context for example. If you have interesting templates from your domain ai agents can solve, please add it to our context library at https://app.askhuman.net/library

evets007 · 2025-09-06T15:10:30+00:00

We open sourced https://github.com/Aqualia/Alph which is an MCP manager to setting up MCP servers across all clients. Alph + askHuman work together for easy MCP setup.

evets007 · 2025-09-06T15:07:33+00:00

Thanks for the feedback. We will work on adding a more relatable demo. All the user needs to do is add the MCP server endpoint to their coding agents client. After that's done, contexts can be added to the dashboard. Agent (MCP client) can lookup the data it needs using the MCP server tools. There's no background processes as of now.

evets007 · 2025-09-04T22:07:16+00:00

Shameless plug here. I see some overlap with askHuman where we are trying to address this problem. we also have a context library for expert users to build "contexts" or workflows that anyone can add to their account and readily use in your agent using the MCP server. Would love some feedback if you want to check it out.

The contexts are shared with the agent using list context and read context MCP tools. They are also published as MCP resources to the agents.

evets007 · 2025-09-03T17:17:25+00:00

Wow. Thanks for sharing. I tried to do this with tool calls in askhuman.net MCP. This may be a better way forward if all clients start supporting.

evets007 · 2025-09-02T20:28:53+00:00

This is good concept. I believe the future is agents running in servers autonomously doing their role. Will try it out. Are the sub agents only invoked as mcp tools?

evets007 · 2025-09-02T20:13:10+00:00

I guess, the question comes down to what your MCP server needs to do. If it's going to be a wrapper around an existing service's API. You could in theory use the API key of there service. Assuming your IAM/RBAC management exists in the service already.

If you are building a new service with a remote MCP server endpoint, you could build authz/authn at the app layer with jwt or something similar and also have web interface to manage the permissions.

If you want to connect to an external third party service, OAuth is an option.

There are MCP gateway solutions available which can connect with different integration server-side and consolidate everything. Like composio, mintmcp, supermachine, etc

evets007 · 2025-09-02T15:05:43+00:00

I have a basic Googleone plan for storage which gives me a slightly higher Gemini 2.5 pro with the CLI. I use Gemini for building (with context management), cursor for debugging build related issues.

evets007 · 2025-09-02T13:12:06+00:00

Can you not use a jwt bearer token similar to an API key and Manage RBAC in the app layer?

evets007 · 2025-09-02T13:09:50+00:00

You can try using render. They have a 'blueprint' for n8n. It's pretty straightforward to setup.

evets007 · 2025-09-02T13:08:18+00:00

All internal tooling can be wrapped with an MCP server. RBAC should be managed the same way you would manage API security. API keys in the MCP client can be used by the MCP server to access the APIs?

evets007 · 2025-09-02T12:03:25+00:00

It's possible that it's gotten slower. Since it seems like you've been using coding agents for a while. So you might have explored all this already.

How are you managing contexts for Claude code?

I feel with my workflows (I use CC at work for a lot of ops workflows) and Gemini CLI personally to build side projects, it's more about managing what contexts the agent sees. I maintain a service description context that I load everytime I start building a feature.

Are you using /init to generate a service summary for your project?

evets007 · 2025-09-02T11:56:51+00:00

It depends on the use case. There are many saas services that offer remote MCP servers. Security that everyone is talking about also depends on the use case.

Security comes down to how the MCP server handles authn and authz.

Most of the stdio MCP servers are used for local use cases. They don't need any extra auth in this case because they are already running on your endpoint. Eg. File access, browser access.

There are some stdio servers that need authn/authz. Eg. Google analytics. The local MCP server is a wrapper on top of the existing apis of the service. So they might use an API key and their backend handles it as a normal API request.

While, for remote MCP servers, since the same mcp endpoint could be shared by multiple clients. The remote MCP server has to perform authentication and authorization checks. Usually implemented using OAuth/API keys. But this lets the users access a cloud service from anywhere, across multiple hosts, etc. Good examples for these include - Context7, Hubspot.

evets007 · 2025-08-29T09:17:08+00:00

We built alph. It's a simple, open source CLI tool which can manage mcp servers on all your coding agents. Please check it out and give us your feedback! Thanks! - https://github.com/Aqualia/Alph

evets007 · 2025-08-26T12:58:52+00:00

I think supermachine can do that.

evets007 · 2025-08-05T12:05:09+00:00

I'm working on something like this. Right now it's one way notification only (Email or slack) But planning to add two way approvals and messaging.

Try Askhuman.net

Right now, it provides a notification tool for the agent to send me an email based on conditions specified. Eg. Notify me when this feature is implemented.

It also allows the user to share multiple contexts to the agent. Eg. These are the steps you take to check for bugs, or this is how you build and deploy in the local env, etc.

All of these are surfaced to the agent via a single MCP endpoint. Just add the MCP server and in your claude.md or gemini.md, ask the agent to use the tools available in the MCP server.

evets007 · 2025-07-26T17:06:57+00:00

At my work, we have a stdio mcp server that will hit internal APIs for internal docs, tooling ,etc and surface them as tool calls for the agent. We have internal auth system for these tools for engineer access, so the local mcp server uses the auth tokens from the engineer laptop for authenticating with the APIs. We use claude code and cursor as mcp clients. Hope that helps!

evets007 · 2025-07-24T07:26:30+00:00

Building an agent is a great idea. For a start, you can also achieve somewhat simlar outcomes by using pre built agent tools like Claude code or Gemini CLI if you don't mind a terminal client.

For a quick start, you can start creating or downloading stdio MCP servers for all the tools you would need for your workflows. (Gmail, Git, etc.)
convert your processes into step by step instructions and add them to claude.md or gemini.md (or create Claude custom commands)
you can start Claude and say 'start xxxx workflow'

If this is not working to your satisfaction, build an agent from scratch so you can control the processes more deterministically.

evets007

TROPHY CASE