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

# MCP connections

> Connect ChatGPT, Claude, and other AI clients to Silo through remote MCP and per-user OAuth.

Silo exposes a remote MCP server over Streamable HTTP:

```text theme={"system"}
$SILO_API_URL/mcp
```

The server uses the same OAuth scopes, user permissions, tenant isolation, and
transactional write pipeline as the REST API. It supports OAuth discovery and
Dynamic Client Registration, so compatible clients can register and authorize
without a manually copied bearer token.

## Available tools

The server exposes list, search, get, create, update, and delete tools for:

* articles
* books
* magazines and issues
* knowledge files, including a separate content-read tool
* CRM contacts and companies

Article tools require a `siteId`; issue tools require a `magazineId`. Mutating
tools accept an optional `idempotencyKey`. Use one for every requested write,
especially when an AI client may retry a tool call.

Read tools are marked read-only. Create and update tools are marked mutating,
and delete tools are marked destructive, allowing supporting clients to apply
their own review and confirmation policy.

## Connect ChatGPT

ChatGPT's current full MCP and write-action flow is available through developer
mode on supported workspace plans. Availability and labels can change while
the feature is in beta; check
[OpenAI's current developer-mode guide](https://help.openai.com/en/articles/12584461-developer-mode-apps-and-full-mcp-connectors-in-chatgpt-beta)
before rollout.

1. Have a workspace admin enable developer mode and custom MCP apps.
2. Open the workspace or user Apps settings and choose to create an app.
3. Enter `$SILO_API_URL/mcp` as the MCP endpoint and select OAuth.
4. Scan tools. ChatGPT follows Silo's protected-resource and authorization-
   server metadata and opens Silo sign-in.
5. Sign in, select the intended organization, review the requested scopes, and
   authorize the app.
6. Test read and write tools in a new chat before publishing the app to other
   workspace members.

Silo advertises `offline_access` and issues refresh tokens so ChatGPT can renew
expired access tokens. Each user connects and authorizes separately; an admin
publishing the app does not grant the admin's Silo permissions to other
members.

## Connect Claude

Claude supports OAuth-based Streamable HTTP remote MCP servers and Dynamic
Client Registration. See Anthropic's
[custom connector setup](https://support.anthropic.com/en/articles/11175166-about-custom-integrations-using-remote-mcp)
and
[remote MCP server requirements](https://support.anthropic.com/en/articles/11503834-building-custom-integrations-via-remote-mcp-servers)
for current plan and workspace controls.

1. Open **Settings > Connectors** in Claude or Claude Desktop.
2. For a Team or Enterprise workspace, have an owner add Silo under the
   organization connectors. Pro and Max users can add it in their connector
   settings.
3. Add a custom connector and enter `$SILO_API_URL/mcp`.
4. Choose **Connect**, sign in to Silo, select the intended organization, and
   approve the requested scopes.
5. Enable only the Silo tools needed for the conversation and review write-tool
   approvals before allowing them.

## Other MCP clients

A compatible client must support remote Streamable HTTP plus OAuth protected-
resource discovery. Point it to `$SILO_API_URL/mcp`; do not configure the REST
base URL as the MCP endpoint.

For development diagnostics, use the official MCP Inspector against the same
endpoint and complete the OAuth flow with a non-production test organization.

<Warning>
  AI clients can read and change data with the authorizing user's permissions.
  Grant the narrowest scopes, keep destructive tools disabled when they are not
  needed, and review write arguments before approval.
</Warning>