Model Context Protocol (MCP) Server

Shed exposes a remote HTTP-based Model Context Protocol (MCP) server, enabling AI developer agents, IDE assistants, and LLM workspaces to interface directly with your repositories, schemas, migrations, and seeds.

---

Server Endpoint & Transport

The official Shed remote MCP server is hosted at:

https://mcp.shedb.online/mcp

Property	Value
Server Name	eyegil-shed
Transport Protocol	http (Streamable HTTP / SSE)
Endpoint URL	https://mcp.shedb.online/mcp

---

Session ID Authentication

Every connection to the eyegil-shed MCP server requires a valid Session ID. Shed supports three flexible ways to provide this credential:

1. Header: X-Session-Id (Recommended for VS Code)

X-Session-Id: your-session-id-here

2. Header: session-id (Alternative header)

session-id: your-session-id-here

3. Query Parameter: ?sessionId=... (Best for header-restricted clients)

https://mcp.shedb.online/mcp?sessionId=your-session-id-here

:::tip Query Parameter Compatibility If your MCP client or AI agent does not support specifying custom HTTP headers, simply append ?sessionId=<id> directly to the server URL. Both header and query parameter methods are verified equally. :::

---

Client Configurations

Select your environment below to copy the appropriate MCP configuration:

VS Code

Add the following to your VS Code MCP configuration (e.g., .vscode/mcp.json or extension settings such as Cline / Roo Code):

{
  "servers": {
    "eyegil-shed": {
      "type": "http",
      "url": "https://mcp.shedb.online/mcp",
      "headers": {
        "X-Session-Id": "${input:shed-session-id}"
      }
    }
  }
}

:::info VS Code Input Variable Using ${input:shed-session-id} prompts you securely for your session ID in the VS Code command palette without hardcoding secrets into your workspace files. If you prefer hardcoding, replace it with your actual session ID string. :::

Cursor

Configure in Cursor Settings > Features > MCP, or edit ~/.cursor/mcp.json:

Option A: Using Headers

{
  "mcpServers": {
    "eyegil-shed": {
      "type": "http",
      "url": "https://mcp.shedb.online/mcp",
      "headers": {
        "X-Session-Id": "YOUR_SESSION_ID"
      }
    }
  }
}

Option B: Using Query Parameter

{
  "mcpServers": {
    "eyegil-shed": {
      "type": "http",
      "url": "https://mcp.shedb.online/mcp?sessionId=YOUR_SESSION_ID"
    }
  }
}

Claude Desktop

Add to your claude_desktop_config.json (located at ~/Library/Application Support/Claude/ on macOS or %APPDATA%\Claude\ on Windows):

{
  "mcpServers": {
    "eyegil-shed": {
      "url": "https://mcp.shedb.online/mcp?sessionId=YOUR_SESSION_ID"
    }
  }
}

Or with custom headers (if your desktop build supports HTTP header maps):

{
  "mcpServers": {
    "eyegil-shed": {
      "url": "https://mcp.shedb.online/mcp",
      "headers": {
        "X-Session-Id": "YOUR_SESSION_ID"
      }
    }
  }
}

Windsurf (Codeium)

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "eyegil-shed": {
      "type": "http",
      "url": "https://mcp.shedb.online/mcp",
      "headers": {
        "X-Session-Id": "YOUR_SESSION_ID"
      }
    }
  }
}

Zed Editor

In your Zed settings (~/.config/zed/settings.json), add the server to context_servers:

{
  "context_servers": {
    "eyegil-shed": {
      "endpoint": "https://mcp.shedb.online/mcp?sessionId=YOUR_SESSION_ID"
    }
  }
}

cURL / Testing

Quickly test connectivity from your terminal:

# Using X-Session-Id header
curl -X POST "https://mcp.shedb.online/mcp" \
  -H "X-Session-Id: YOUR_SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "tools/list", "id": 1}'

# Or using query parameter
curl -X POST "https://mcp.shedb.online/mcp?sessionId=YOUR_SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "tools/list", "id": 1}'

---

Available MCP Tools

Once connected, your AI assistant gains access to the following built-in Shed tools:

Tool Name	Parameters	Description
sync_changelog	namespace, repository	Synchronizes the complete changelog (schema, migrations, seeds) into agent context.
get_schema	namespace, repository	Inspects the current compiled database DDL and schema checksum.
list_migrations	namespace, repository	Lists all forward and rollback migrations in chronological order.
get_migration	namespace, repository, migrationId	Retrieves specific forward and rollback SQL statements.
list_seeds	namespace, repository	Lists available database seed datasets and verification hashes.
get_seed	namespace, repository, seedId	Reads SQL content and target schema for a specific seed.

---

Troubleshooting & Verification

Connection Checklist

1. Verify Session ID: Ensure your session ID is active and entered without leading or trailing spaces.
2. Protocol Check: Ensure type is set to http (or sse in clients that separate HTTP streaming).
3. Firewall / Proxy: The endpoint mcp.shedb.online requires outbound HTTPS access on port 443.
4. Header vs Query Param: If your agent fails with 401 Unauthorized when using headers, switch to the URL query parameter format:

   https://mcp.shedb.online/mcp?sessionId=<YOUR_SESSION_ID>