← Agent setup

VS Code (Copilot)

Add an HTTP server entry to the workspace .vscode/mcp.json.

Updated

Add to Claude

1. Get a token

A workspace owner issues a credential at /mcp. Start with read-only scopes: article:read, brand:read, campaign:read. Export it in your shell profile (VS Code asks for the token itself, so only step 3 uses it):

export UPRANK_MCP_TOKEN="<your token>"

2. Register the server

.vscode/mcp.json

Endpoint https://uprank.devino.ca/api/mcp, streamable HTTP with a bearer header filled in from a token input. VS Code prompts for the token the first time the server starts.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "uprank-token",
      "description": "uprank MCP token",
      "password": true
    }
  ],
  "servers": {
    "uprank": {
      "type": "http",
      "url": "https://uprank.devino.ca/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:uprank-token}"
      }
    }
  }
}

Check that VS Code (Copilot) loaded the server

Run MCP: List Servers from the Command Palette and select uprank to start, stop or restart it, or to show its output. It is also listed under MCP SERVERS - INSTALLED in the Extensions view.

3. Verify

Ask the agent to call article_list with { "pageSize": 1 }. A JSON result with items and nextCursor means the connection and scopes are good. A 401 means the token is missing, revoked, expired, or a dev: credential used against production.

4. Next steps

Ask VS Code (Copilot) in plain language; it picks the tool. These work with the read-only token.

  • List my five most recent uprank articles with their status.

    article_list

  • Summarize my site's uprank brand profile: voice, audience and proof points.

    brand_get

  • Which of my uprank articles have an expired claim or no current quality score?

    refresh_list

Ready for drafts? Issue a second token that adds research:run, article:write, quality:run and ask for the create_quality_article prompt with a site id and either a campaign id and a topic to research or an existing topic opportunity id. It researches, drafts and scores an article against the quality gates and stops before publishing.

Troubleshooting VS Code (Copilot)

Why does the VS Code config ask for the token instead of reading UPRANK_MCP_TOKEN?
An open VS Code issue (microsoft/vscode#336232) reports that ${env:} in mcp.json headers is sent literally, which uprank rejects with a 401. With ${input:uprank-token}, VS Code prompts the first time the server starts and stores the value securely for later starts.
VS Code shows an error for uprank in the Chat view. Where are the details?
Select the error and choose Show Output, or run MCP: List Servers, select uprank and choose Show Output. A 401 there means the token you entered is missing, revoked, expired, or a dev: credential used against production.
Why doesn't the uprank server in .vscode/mcp.json start?
Workspace MCP servers inherit Workspace Trust, and in restricted mode VS Code blocks workspace MCP configuration. Trust the workspace, or run MCP: Open User Configuration and add the same entry there to use uprank in every workspace.
Why is uprank missing from a VS Code Agent Host session?
VS Code forwards .vscode/mcp.json servers to the Agent Host except those that need interactive input, such as ${input:...} variables, so this entry is not forwarded. The Agent Host reads workspace .mcp.json and ~/.copilot/mcp-config.json natively.

No workspace yet?

Tokens belong to a workspace. Create one, then come back to step 1.