Site vs SaC — Software as Content

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Site has no confirmed install command yet — follow its own setup instructions.

Site has no declared pricing — check the project's own site. Auth: no auth required. SaC — Software as Content is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add site-259 and sac-software-as-content as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Site has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. SaC — Software as Content has 45/100 (Fair) with 3 views, 0 installs and 3 GitHub stars.