CoSchedule

com.coschedulePublished by coschedule.comOfficial publisherv1.0.0Updated Oct 24, 2026

Ask about your CoSchedule marketing calendar: projects, campaigns, tasks and social posts.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query a CoSchedule marketing calendar for projects, campaigns, tasks and social posts.

What you can do
This remote MCP server connects an assistant to a CoSchedule marketing calendar. Based on the description, it answers questions about projects, campaigns, tasks and social posts held in that calendar. No individual tools are listed in the supplied material, so the exact operations are not documented here.
When to use it
Worth considering when a team keeps its marketing planning in CoSchedule and wants an assistant to look up calendar items such as campaigns, projects, tasks or scheduled social posts during a conversation.
Requirements
A remote streamable HTTP endpoint at platform.coschedule.com. OAuth authentication is required, so a CoSchedule account with access to the relevant calendar is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a CoSchedule account, so the assistant may see marketing calendar content belonging to that account. The supplied description does not state whether the server can only read data or can also create, change or delete items; confirm the granted scopes before installing.

Installation

In SourceWeft

  1. Open CoSchedule in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.coschedule%2Fcoschedule/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "coschedule": {
      "type": "http",
      "url": "https://platform.coschedule.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.