# Sloan / Reference / Mcp Json Reference Documentation – TypeScript

## Included Files
1. sloan/reference/mcp-json-reference/mcp-json-reference.mdx

## Getting Started

Source: sloan/reference/mcp-json-reference/mcp-json-reference.mdx

Getting started guide for Sloan

CTACard,
  CTACards,
  ZoomImg,
  ChipButton,
  Columns,
  Column,
  FeatureCard,
  FeatureGrid,
  BulletPointsCard,
  QnABullets,
  CheckmarkBullets,
  Icons,
} from "@/components";

## Configuring Sloan MCP with MCP.JSON

- **Node**: [version 20+](https://nodejs.org/en/download) (LTS recommended)
- **Anthropic API key**: [Get your API key from Anthropic](https://docs.anthropic.com/en/docs/initial-setup). This is required for using Sloan's generative MCP tools.
- **Moose CLI** and Moose Project required for "write" tools. 

### Where is your MCP.JSON file?

Your MCP.JSON file is located in a different location depending on your client of choice. The below is a list of default locations for the MCP.JSON file for our supported clients.

* [Claude Desktop](https://modelcontextprotocol.io/quickstart/user): `~/Library/Application Support/Claude/claude_desktop_config.json` (note, you can create this by going to `claude > settings > Developer > Edit Config`)
* [Cursor (global MCP)](https://docs.cursor.com/context/model-context-protocol#configuration-locations): `~/.cursor/settings/mcp.json`
* [Cursor (project MCP)](https://docs.cursor.com/context/model-context-protocol#configuration-locations): `/path/to/your/project/.cursor/mcp.json`
* [Windsurf](https://docs.windsurf.com/windsurf/cascade/mcp#configuring-mcp-tools): `~/.codeium/windsurf/mcp_config.json`

For other clients, look to their documentation for where their MCP.JSON file is located.

### Adding Sloan MCP to your MCP.JSON file

**Configuration Object Naming**: Different MCP clients use different naming conventions for the server configuration object:
- **Cursor, Windsurf**: Uses `"mcpServers"`
- **Claude Desktop, VS Code**: Use `"servers"` instead

Make sure to check your specific client's documentation for the correct naming convention.

<Tabs.Tab>
```json filename="MCP configuration" copy
{
  "mcpServers": {
    "sloan": {
      "args": [
        "@514labs/sloan-mcp@latest",
        "--moose-read-tools",
        "path/to/your/moose/project"
      ],
      "command": "npx",
      "env": {
        "ANTHROPIC_API_KEY": "<your-anthropic-api-key>",
        "MOOSE_PATH": "path/to/your/moose/installation",
        "NODE_PATH": "path/to/your/node/installation",
        "PYTHON_PATH": "path/to/your/python/installation"
      }
    }
  }
}
```
</Tabs.Tab>
<Tabs.Tab>
```json filename="MCP configuration" copy
{
  "servers": {
    "sloan": {
      "args": [
        "@514labs/sloan-mcp@latest",
        "--moose-read-tools",
        "path/to/your/moose/project"
      ],
      "command": "npx",
      "env": {
        "ANTHROPIC_API_KEY": "<your-anthropic-api-key>",
        "MOOSE_PATH": "path/to/your/moose/installation",
        "NODE_PATH": "path/to/your/node/installation",
        "PYTHON_PATH": "path/to/your/python/installation"
      }
    }
  }
}
```
</Tabs.Tab>

### Arguments / Environment Variables

### Adding tool sets to your MCP.JSON file

In general, we recommend using read-only tool-sets (`moose-read-tools` and `remote-clickhouse`) with chat type clients (like Claude Desktop)

For information about toolsets, see [tools reference](../sloan/reference/tool-reference).

  <Tabs.Tab>
    ```json filename="MCP.JSON" copy
    "args": [
        ...
        "--moose-read-tools",
    ]
    ```
    [Moose read tools documentation](../sloan/reference/tool-reference#moose-read-tools)

  </Tabs.Tab>
  <Tabs.Tab>
    ```json filename="MCP.JSON" copy
    "args": [
        ...
        "--moose-read-tools",
        "--moose-write-tools",
    ]
    ```
    [Moose write tools documentation](../sloan/reference/tool-reference#moose-write-tools)
  </Tabs.Tab>
  <Tabs.Tab>

    ```json filename="MCP.JSON" copy
    "args": [
      ...
      "--remote-clickhouse", 
      ...
    ]
    "env": {
      ...
      "BOREAL_CLICKHOUSE_HOST": "...",
      "BOREAL_CLICKHOUSE_PORT": "...",
      "BOREAL_CLICKHOUSE_USER": "...",
      "BOREAL_CLICKHOUSE_PASSWORD": "...",
      "BOREAL_CLICKHOUSE_DATABASE": "...",
    }
    ```

    [Remote Clickhouse read tools documentation](../sloan/reference/tool-reference#remote-clickhouse)

  </Tabs.Tab>