Browse docs
The connection#
Add SkedCast to Claude Code#
bash
claude mcp add --transport http skedcast https://api.skedcast.com/mcp
# then, inside a Claude Code session:
/mcp/mcp shows connection status and walks you through the browser sign-in. Check that skedcast shows as connected, then ask Claude Code directly ("list my scheduled posts for next week") and it calls the tools for you.
Where the config is stored#
--scope local (the default) keeps the server for you in this project. --scope project writes it to .mcp.json so teammates share it. --scope user makes it available in all your projects.
json
{
"mcpServers": {
"skedcast": {
"type": "http",
"url": "https://api.skedcast.com/mcp"
}
}
}mcpclaude codecliai agent
FAQ
- Do I need an API key?
- No. The OAuth sign-in handles everything: Claude Code finds the authorization server, registers itself and opens a browser for you to sign in and approve. The MCP server does not accept API keys.
- Can I limit which tools Claude Code can use?
- The effective permissions are your account's scopes ∩ your access, as with any MCP client. You can't give Claude Code more than your own SkedCast access allows, and you can approve write-tool calls one by one.