Cursor's agent, past the edge of the repo
One MCP server, only the tools you allow, no key in the config.
gbrain.io
Cursor
One MCP server, only the tools you allow, no key in the config.
Cursor’s agent only knows what is in the repo. The usual fix is several MCP servers, each with its own config and its own API key sitting in a file.
gbrain is one server. You choose which tools the agent sees, and the only credential in your settings is a revocable token.
Not one per service. What this client can call is decided by its permission, not by the address, and the token comes from the client's own page in the workspace, minted once and shown once.
Connect one in the browser and it answers here, under the same permission and the same record as everywhere else.
The other places a connection answers are on Works with, and Tools explains the permission, the ceiling and the record they share.
