Quickstart

MCP quickstart

The Silo MCP gateway speaks Streamable HTTP at a single canonical endpoint. Any spec-compliant MCP client can list and call tools once it has an OAuth bearer for an authorized connection.

Endpoint

URL

https://connect.onesilo.com/mcp

Transport

Streamable HTTP (single POST endpoint, no SSE upgrade required)

Auth

Bearer token from an OAuth connection. Register your client via Dynamic Client Registration (DCR), then complete the user consent flow once per end-user.

1. Register your app (DCR)

Most MCP SDKs do this for you. Manually, POST to the OAuth registration endpoint with your redirect URI(s).

curl -X POST https://api.onesilo.com/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Cool App",
    "redirect_uris": ["https://coolapp.example.com/auth/callback"],
    "grant_types": ["authorization_code", "refresh_token"]
  }'

2. Authorize a user

Redirect the user to https://api.onesilo.com/oauth/authorize with the standard PKCE parameters. After they pick which services to share, Silo redirects back with a code; exchange it at https://api.onesilo.com/oauth/token for a bearer.

See OAuth + services for the full flow including service selection and the auto-provisioned default silo that lands on the connection.

3. List and call tools

list-tools.sh

curl -X POST https://connect.onesilo.com/mcp \
  -H "Authorization: Bearer $SILO_BEARER" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

call-tool.sh

curl -X POST https://connect.onesilo.com/mcp \
  -H "Authorization: Bearer $SILO_BEARER" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "silo_ask",
      "arguments": {
        "silo_id": "default",
        "question": "What did I discuss with Asher last week?"
      }
    }
  }'

The string "default"is a reserved alias for the connection's auto-provisioned default silo — see Default silo.