# Cursor

Configure the local Minds MCP demonstration for a project or personal Cursor setup.

Source: https://docs.minds.sh/docs/agents/cursor



This setup runs `akasha-mcp` as a local process. Its current standalone backend keeps memory only for that process; it is suitable for tool inspection and a local demonstration.

## Add the server [#add-the-server]

Create or update `.cursor/mcp.json` for the project, or `~/.cursor/mcp.json` for a personal configuration:

```json
{
  "mcpServers": {
    "minds-local-demo": {
      "command": "/absolute/path/to/akasha-mcp",
      "args": ["--transport", "stdio", "--namespace", "local-demo", "--agent-id", "cursor"]
    }
  }
}
```

Merge the entry with existing servers. Replace the executable path with the installed binary. Cursor supports local command-based MCP servers and these project/global configuration locations. See the [official Cursor MCP documentation](https://docs.cursor.com/context/model-context-protocol).

## Confirm tool behavior [#confirm-tool-behavior]

Inspect Cursor's MCP server status and the tools it discovered. Ask its agent to recall a non-sensitive phrase. To test storage, remember a small test record and recall it while the same server process stays alive.

A green connection badge does not establish a persistent dedicated-Mind connection. `--endpoint` on this standalone binary does not switch its default in-memory backend to the daemon. Use [HTTP tools](/docs/agents/http-tools) from your own tool adapter when you need the actual instance.

## Avoid the outdated helper command [#avoid-the-outdated-helper-command]

The checked-in `cogs mcp setup-cursor` helper writes a command containing `akasha mcp serve`; the CLI has no such action. The configuration above invokes the actual `akasha-mcp` binary and names its local scope explicitly.

Keep private credentials outside a committed project configuration. This local demonstration does not need a production instance capability because it does not connect to that instance.