# Use Jarvis from your tools
URL: https://jarvis.ceo/docs/mcp/use-jarvis-from-your-tools
Status: beta

Jarvis publishes an MCP server (jarvis-memory) that exposes your memory and connected apps, so a coding agent like Claude Code, Cursor, or Codex can use what Jarvis knows.

> [beta] Exposing Jarvis over MCP is part of the beta, in early access. Download the beta, or join the waitlist for full access.

Jarvis does not only use other tools, it can be one. It publishes an MCP server named jarvis-memory that exposes what Jarvis knows about you and the apps it is connected to.

## What your agent gets

- Memory: the people, projects, places, and preferences Jarvis has learned.
- Connected tools: actions in the apps you connected, like Gmail, Calendar, and Slack.

## Add it to your agent

Add the jarvis-memory server to your coding agent using the standard mcpServers format. Jarvis generates the exact entry for you, with the right paths filled in.

```json
{
  "mcpServers": {
    "jarvis-memory": {
      "command": "node",
      "args": ["/path/to/Jarvis/mcp-server.js"],
      "env": { "JARVIS_HOME": "~/.jarvis" }
    }
  }
}
```

## What you can do

In Cursor, ask your agent to draft a reply using what Jarvis knows about the person, or to check your calendar before proposing a time, without leaving the editor.

Related: Connect an MCP server (https://jarvis.ceo/docs/mcp/connect-a-server), Memory (https://jarvis.ceo/docs/jarvis-2-0/memory)