Setup guide · MCP

Set up seenpaid in GitHub Copilot

GitHub Copilot is GitHub’s assistant, here in VS Code’s agent mode. Copilot in agent mode can use any MCP server VS Code knows about. It has no connection to your social accounts until you add one — with seenpaid added, “post the release notes” is a request it can actually carry out.

Card required, no charge until day 8. MCP access is on every plan.

$
Endpoint
api.seenpaid.com/mcp
Transport
Streamable HTTP
Auth
Bearer sp_…
Tools
50

Four steps

How to connect GitHub Copilot to seenpaid

You need a seenpaid API key and one paste.

  1. 1

    Create an API key

    In seenpaid, open Settings → API keys and create a key. It starts with sp_ and is shown once, so copy it straight into the next step. You can revoke it at any time.

    Open Settings → API keys
  2. 2

    Add seenpaid to GitHub Copilot

    Save this as .vscode/mcp.json in your project, or run “MCP: Open User Configuration” from the Command Palette to add it for every workspace. The key is not written into the file: VS Code asks for it once, masked, and stores it securely.

    .vscode/mcp.json
    {
      "inputs": [
        {
          "type": "promptString",
          "id": "seenpaid-key",
          "description": "seenpaid API key",
          "password": true
        }
      ],
      "servers": {
        "seenpaid": {
          "type": "http",
          "url": "https://api.seenpaid.com/mcp",
          "headers": { "Authorization": "Bearer ${input:seenpaid-key}" }
        }
      }
    }

    Replace sp_your_api_key with your key.

    Checked against the official docs: code.visualstudio.com/docs/agents/reference/mcp-configuration — "servers" with "type": "http", "url", "headers", and promptString inputs with "password": true.

  3. 3

    Restart and verify

    Run “MCP: List Servers” from the Command Palette and start seenpaid. Then open Copilot Chat in Agent mode and check the tools picker lists seenpaid.

  4. 4

    Ask for your first post

    Start with “Which of my social accounts are connected?” — GitHub Copilot calls list_accounts and names your channels. If none are connected yet, ask for a connect link: that one step needs you in a browser.

Try asking

First things to ask GitHub Copilot

Plain requests. Under each one, the seenpaid tools GitHub Copilot calls to answer it.

  • Which of my social accounts are connected?

    Callslist_accounts
  • Turn the release notes in CHANGELOG.md into a post and schedule it to LinkedIn and X for tomorrow at 10am.

    Callsvalidate_postschedule_post
  • Queue these five tips as posts, one per weekday next week.

    Callsbulk_schedule
  • Which channel brings in the most revenue per post?

    Callsget_channel_roi needs revenue tracking

Revenue tracking is optional and off by default. Scheduling works without it. Every tool →

Troubleshooting

If it does not connect

401 Unauthorized

The request reached seenpaid but no valid credential came with it. Check the key starts with sp_, was not revoked, and is sent as “Authorization: Bearer sp_…” with the word Bearer and one space. seenpaid also answers 401 when the workspace has no active trial or plan, even with a correct key.

Wrong URL, or the server never connects

The endpoint is exactly https://api.seenpaid.com/mcp — not seenpaid.com, and not an /sse URL. seenpaid speaks Streamable HTTP only; a client set to SSE will not connect. Opening the URL in a browser shows a short explainer page, which is expected.

OAuth or API key — which one?

Config files and command-line clients send the sp_ key as a header. Connector screens in apps (claude.ai, Claude Desktop, ChatGPT, Grok) have no key field: they sign in to seenpaid with OAuth instead. Never paste your key into an OAuth client ID or secret field.

VS Code never asked for my key

The prompt appears the first time the server starts. Start it from “MCP: List Servers”. If you entered the wrong key, run “MCP: Reset Cached Tools” or edit the stored input and start it again.

FAQ

GitHub Copilot and seenpaid, answered

Not on its own — it has no credentials for your accounts. Connected to seenpaid’s MCP server it can schedule and publish to the 21 platforms seenpaid supports, and report back per platform what went out.

Create an API key in seenpaid under Settings → API keys, then add https://api.seenpaid.com/mcp as a remote MCP server with the key sent as an Authorization: Bearer header. Save this as .vscode/mcp.json in your project, or run “MCP: Open User Configuration” from the Command Palette to add it for every workspace. The key is not written into the file: VS Code asks for it once, masked, and stores it securely.

Use all 50 seenpaid tools: schedule, edit and cancel posts, check each platform’s limits before publishing, generate images and carousels, and read what published. Revenue tools (which post made money) work only if you switch on revenue tracking, which is optional and off by default.

No. MCP access is included on every seenpaid plan and in the 7-day trial.

It acts through a key or sign-in scoped to one seenpaid workspace; an API key can be revoked in Settings at any time. No tool returns your social passwords or platform tokens, and it cannot connect a new account on its own: it hands you a link and you sign in.