Sprid speaks the Model Context Protocol over HTTP at https://api.sprid.studio/api/mcp . Claude Code, Claude Desktop, and OpenAI Codex CLI all support remote MCP natively in 2026 — no bridge process needed. Authentication is a personal access token issued from /settings/tokens in your Sprid app.
Visit /settings/tokens in your Sprid instance. Create a token, then copy the snippet for whichever client you’re using. The raw token is shown only once — anything stored on Sprid is just a SHA-256 hash.
One command, HTTP transport, runs from anywhere. Restart Claude Code after install, then ask it to list my Sprid accounts to confirm.
claude mcp add --transport http sprid \
https://api.sprid.studio/api/mcp \
--header "Authorization: Bearer sprd_..." Open Claude Desktop → Settings → Developer → Edit Config. Paste the entry below into claude_desktop_config.json (merging with any existing mcpServers object), save, then quit-and-relaunch the app.
// claude_desktop_config.json
{
"mcpServers": {
"sprid": {
"type": "http",
"url": "https://api.sprid.studio/api/mcp",
"headers": { "Authorization": "Bearer sprd_..." }
}
}
} Codex CLI 0.20+ supports remote HTTP MCP servers natively. Use codex mcp add to let the CLI write ~/.codex/config.toml , or paste the TOML block manually.
# Option A — codex mcp add (recommended, writes ~/.codex/config.toml)
export SPRID_PAT=sprd_...
codex mcp add sprid --url https://api.sprid.studio/api/mcp \
--bearer-token-env-var SPRID_PAT
# Option B — paste into ~/.codex/config.toml
[mcp_servers.sprid]
url = "https://api.sprid.studio/api/mcp"
[mcp_servers.sprid.http_headers]
Authorization = "Bearer sprd_..." 40+ tools cover accounts, posts, slides, formats, lines, images, templates, fonts, guardrails, reflections, and publishes. Resources expose sprid://account/{slug}, sprid://post/{id}, and the workspace + archetype catalogs.
Call tools/list after connecting to introspect the full JSON Schema for every tool — descriptions live alongside the schema so the agent picks correctly without extra prompting.
Sprid’s MCP surface mirrors the publish sheet exactly, so a short script can ship a post end to end:
- draft_post_from_hook → scaffold + AI-fill a post from a single hook line.
- render_post_preview → server-render every slide to PNG and get back R2 URLs you can feed straight into a publish.
- schedule_post with nextFreeSlot: true → walks the account calendar, skips days that already have a publish on the chosen platform, and books the first open slot at the time you choose (default 09:00 in the account timezone).
- next_schedule_slot → preview the slot without booking it; useful for dry runs or building a batch plan.
TikTok publishes require a full options payload (privacy level + interaction toggles) — the agent will fall back to account.config.publishDefaults.tiktok if you’ve set one in the app, so most calls don’t need to repeat it.