> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jsonsilo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a Client

> Add the JSONsilo MCP server to Claude Code, Cursor, VS Code, or another client

## Introduction

This guide shows how to add the JSONsilo MCP server to your AI tool. You need an [MCP Key](https://docs.jsonsilo.com/keys/mcp-keys.md) first.

> [!TIP]
>
> The console builds these snippets for you. Right after you create a key, the **MCP key created** dialog shows them with your real key filled in. Later, click `Connect a client` on the **MCP keys** tab to see them again with a placeholder.

## Connection Details

| | |
| - | - |
| **Server URL** | `https://mcp.jsonsilo.com/mcp` |
| **Header** | `Authorization: Bearer jsmcp_YOUR_KEY` |

In every example below, replace `jsmcp_YOUR_KEY` with one of your MCP keys.

## Setup

> [tab] Claude Code
>
> Run this in your terminal:
>
> ```bash Terminal theme={null}
> claude mcp add --transport http jsonsilo https://mcp.jsonsilo.com/mcp --header "Authorization: Bearer jsmcp_YOUR_KEY"
> ```
>
> Add `--scope user` to make the server available in every project.

> [tab] Cursor
>
> Add this to `~/.cursor/mcp.json`, or merge it into the `mcpServers` you already have:
>
> ```json ~/.cursor/mcp.json theme={null}
> {
>   "mcpServers": {
>     "jsonsilo": {
>       "url": "https://mcp.jsonsilo.com/mcp",
>       "headers": {
>         "Authorization": "Bearer jsmcp_YOUR_KEY"
>       }
>     }
>   }
> }
> ```

> [tab] VS Code
>
> Run **MCP: Open User Configuration** from the Command Palette and add this server:
>
> ```json mcp.json theme={null}
> {
>   "servers": {
>     "jsonsilo": {
>       "type": "http",
>       "url": "https://mcp.jsonsilo.com/mcp",
>       "headers": {
>         "Authorization": "Bearer jsmcp_YOUR_KEY"
>       }
>     }
>   }
> }
> ```

> [tab] Other
>
> Any MCP client that supports Streamable HTTP and custom headers can connect with these two values:
>
> * **Server URL**: `https://mcp.jsonsilo.com/mcp`
> * **Header**: `Authorization: Bearer jsmcp_YOUR_KEY`
>
> Check your client's documentation for where to enter them.

> [!WARNING]
>
> These snippets contain your key. Keep them out of files you commit.

## Check the Connection

Ask your assistant:

```text theme={null}
List my JSONsilo silos.
```

The assistant should call the `list_silos` tool and show your silos. If it does, you are connected.

You can also check from the terminal. This asks the server for its list of tools:

```bash Terminal theme={null}
curl -X POST https://mcp.jsonsilo.com/mcp \
  -H "Authorization: Bearer jsmcp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-11-25" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
```

A working key returns `200` with the tool list. A key that doesn't work returns one of the errors below.

## Troubleshooting

When a request is refused, the server answers with a status code and a JSON body such as `{ "error": "Invalid MCP key" }`.

| Status | Message | What to do |
| - | - | - |
| `401` | `Missing MCP key. Send Authorization: Bearer <your MCP key>.` | Your client isn't sending the header. Check the header name and the `Bearer ` prefix. |
| `401` | `Invalid MCP key` | The key is wrong, was deleted, or isn't an MCP key. Access Keys and Manage Keys don't work here. |
| `401` | `MCP key expired. Create a new key in the JsonSilo console.` | Create a new [MCP Key](https://docs.jsonsilo.com/keys/mcp-keys.md) and update your client. |
| `403` | `MCP is not available on your plan. Please upgrade your plan.` | Your plan doesn't include MCP. [Change your plan](https://docs.jsonsilo.com/billing/upgrade-plan.md). Your keys work again once you do. |
| `402` | `Trial ended` | Your free trial is over. [Choose a plan](https://docs.jsonsilo.com/billing/upgrade-plan.md). |
| `429` | `Request limit exceeded` or `Daily limit exceeded` | You hit a [rate limit](https://docs.jsonsilo.com/rate-limits.md). Wait and try again. |

> [accordion] The assistant can read silos but can't change them
>
> The key is **Read only**. Write tools are hidden from the assistant with this kind of key. Create a new key with **Read & write** access.

> [accordion] A write fails with a schema error
>
> The silo has a locked schema and the new data doesn't match it. The error names the invalid value. Ask the assistant to fix the data, or change the schema in the console. See [Schema Lock](https://docs.jsonsilo.com/features/schema-lock.md).

> [accordion] The assistant only gets a summary of my silo
>
> The silo is over 100 KB, so it is not returned whole. Ask the assistant for the specific part you need. See [MCP Tools](https://docs.jsonsilo.com/mcp/tools.md#large-silos).

> [accordion] My browser-based tool can't connect
>
> The MCP server is built for desktop and command-line clients. It doesn't accept requests from web pages.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.