Koskamo

FeedSquad MCP

FeedSquad MCP enables AI agents to draft, schedule, and publish marketing content to LinkedIn, X, and Threads. It features an approval-first workflow where drafts are reviewed before publishing, includes a shared brand memory system called Stash, and provides tools for campaign management, calendar viewing, and platform connection via OAuth.

Visit FeedSquad

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

FeedSquad MCP logo, by FeedSquadVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Operated by FeedSquad
You need:OAuth 2.1 with PKCEaccount access and plan limits applyX publishing and MCP media attachments require paid Handlerget_brand_context, get_brain_gaps, tell_stash and propose_stash_items require per-account enablement and Stash scopes
MCP endpoint (Streamable HTTP)
https://feedsquad.com/api/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to feedsquad.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Draft and schedule posts for LinkedIn, X, and Threads
  • Approve or cancel draft posts before publication
  • Retrieve brand voice and context from Stash memory
  • Create and manage multi-post content campaigns

Source and maintenance

Vendor evidenceRegistry 1.5.2
mcp-registry: com.feedsquad/feedsquad@1.5.2Project website

Protocol and capabilities

Server
feedsquad 1.5.2
MCP protocol negotiated in check
2025-11-25
Tools
Sign-in required
Resources
Sign-in required
Resource templates
Sign-in required
Prompts
Sign-in required
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Tools

Sign-in required

No tool definitions available.

Prompts

Sign-in required

No prompt definitions available.

Resources

Sign-in required

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
2668 ms
95th percentile latency
2668 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 2668 ms · metadata changed · refuses unauthenticated tools/list (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http feedsquad-mcp https://feedsquad.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add feedsquad-mcp --url https://feedsquad.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable feedsquad-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "feedsquad-mcp": {
      "url": "https://feedsquad.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "feedsquad-mcp": {
      "type": "streamableHttp",
      "url": "https://feedsquad.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start feedsquad-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "feedsquad-mcp": {
      "type": "http",
      "url": "https://feedsquad.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http feedsquad-mcp https://feedsquad.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://feedsquad.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "feedsquad-mcp": {
      "serverUrl": "https://feedsquad.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like FeedSquad MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,246

Do you run FeedSquad MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing