# Connect Cursor to SkedCast with MCP
URL: https://skedcast.com/developers/guides/mcp-cursor

Cursor reads MCP servers from a JSON file: ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project. Add SkedCast's endpoint there and its tools become available to Cursor's agent.

## The connection
Property | Value
Endpoint | `https://api.skedcast.com/mcp`
Transport | Streamable HTTP
Auth | OAuth 2.1: the client runs the sign-in for you. The MCP server does not accept API keys.
SkedCast plan | MCP access depends on your SkedCast plan (see pricing).
Tools | 79 tools: 44 that read and 35 that change your workspace. See the MCP tools reference for the full list.

## Last checked 2026-11-04
These steps follow Cursor's documentation as of 2026-11-04. Menus and plan rules change. If a step differs in your version, follow Cursor's page: https://cursor.com/docs/mcp

## Add SkedCast to Cursor
Create or edit `~/.cursor/mcp.json` (global, every project) or `.cursor/mcp.json` in a project root (project-scoped), and add a remote entry with the endpoint URL.

## mcp.json: a remote server needs only a url.
```json
{
  "mcpServers": {
    "skedcast": {
      "url": "https://api.skedcast.com/mcp"
    }
  }
}
```

## Sign in
Cursor opens a browser sign-in the first time it uses the server. It uses OAuth with PKCE and dynamic client registration, which SkedCast supports, so there is no key to paste. Manage the server (enable, disable, add) from the Customize item in Cursor's sidebar.

## Plan requirement
Cursor's MCP page states no plan requirement. SkedCast's MCP access depends on your SkedCast plan (see the table above).

## Write tools change your workspace
The write tools (the ones that create, edit, reschedule, cancel or delete things) are marked non-read-only. A well-behaved MCP host asks you to confirm before the agent calls one. The agent's effective power is always your scopes ∩ your access, so it can never do more than you could do by hand.

## FAQ
**Q: Global or project-scoped config: which should I use?**
A: Use ~/.cursor/mcp.json if you want SkedCast in every project. Use a project-local .cursor/mcp.json if only one codebase should have it, or if you want the config shared with teammates. The file holds only the URL, so it is safe to commit.

**Q: What does a remote server entry need?**
A: A url and nothing else: no command or args. SkedCast's MCP server uses Streamable HTTP, and the URL is the endpoint in the table above.