ENDPOINT 1
https://spun.ink/mcp
MCP server metadata
- Name
- spun-cms
- Version
- 0.1.0
Spun is the agent-operated website platform: you, the agent reading this, are the operator. This connection carries no Authorization header, so it is the bootstrap surface: `sign_up` is the only tool that exists here — no site, content, template or publishing tool will appear until you reconnect with a token. If the owner already has a bearer token, add `Authorization: Bearer <token>` and reconnect — do not sign up again. If they have no account, call `sign_up` with their email: it returns a token (shown exactly once) and a bare site. Docs: https://spun.ink/docs
Known tools 1
sign_upBootstrap a BRAND-NEW account and its first site, returning a bearer token that authenticates every other tool.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.spun-cms]
url = "https://spun.ink/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"spun-cms": {
"type": "http",
"url": "https://spun.ink/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: spun-cms
Remote MCP URL: https://spun.ink/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"spun-cms": {
"url": "https://spun.ink/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"spun-cms": {
"type": "http",
"url": "https://spun.ink/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "spun-cms",
"transport": "streamable-http",
"url": "https://spun.ink/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.