1. Open mcp.json#
Edit ~/.cursor/mcp.json to add SkedCast to every project, or .cursor/mcp.json to add it to one repository. You can also install and manage servers from Cursor's Customize page.
2. Add SkedCast as a remote server#
Add an entry with a url (example below). Do not use command and args; that form is for local stdio servers.
3. Sign in#
The first time Cursor uses the server, it opens a browser sign-in. Approve the SkedCast scopes it asks for.
mcp.json (OAuth)#
json
{
"mcpServers": {
"skedcast": {
"url": "https://api.skedcast.com/mcp"
}
}
}Requirements#
Before you connect:
- SkedCast: a plan that includes MCP access (see pricing). The connection acts as you, with your role and plan limits.
- Cursor: no plan requirement is documented.
- On a team, an admin can manage MCP servers under Team Settings > MCP Configuration.
Cursormcpai agents
FAQ
- Does Cursor support OAuth for remote MCP servers?
- Yes. Cursor opens a browser sign-in on first use, and that is the only way to connect: SkedCast's MCP server accepts OAuth access tokens, not API keys.
- What can an agent do once it's connected?
- Whatever your SkedCast role and plan allow. The connection acts as you, not with elevated access. It can read posts and analytics, schedule and revise posts, and act on approvals, through the tools listed on the MCP hub.