How to Use the Pics.io MCP in VS Code Copilot

Q: Can I search for Pics.io assets from VS Code Copilot?

You can ask the VS Code Copilot chat agent to run searchassets. It returns the matching Pics.io files, tags, and IDs right in your VS Code Copilot sidebar.

Equip your development team with direct access to your Pics.io media library inside VS Code Copilot with this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Pics.io MCP to VS Code Copilot

Create your Vinkius account to connect Pics.io to VS Code Copilot — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Pics.io with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Team-wide asset integration in VS Code Copilot

The `list_assets` tool lets your team inspect Pics.io files in specific collections directly from their shared VS Code Copilot workspace. By committing the configuration file to your git repository, every developer gets instant access to the Pics.io media library in VS Code Copilot. This makes Pics.io asset linking fast inside VS Code Copilot. Your VS Code Copilot agent pulls image references and descriptions, allowing developers to insert correct Pics.io URLs into markdown files or code blocks without leaving the editor.

Manage shared collections from your editor

The `create_collection` tool allows your agent to build new folders in your Pics.io media library directly from VS Code Copilot. If a developer is setting up a new project branch in VS Code Copilot, the agent can automatically spin up a matching folder in your Pics.io DAM. This keeps your Pics.io digital assets structured alongside your VS Code Copilot codebase. Your VS Code Copilot team can also run `delete_collection` to clean up temporary Pics.io staging folders once a feature goes live.

Track revisions and feedback inline

The `list_revisions` tool retrieves the history of any Pics.io asset to verify which version is currently active in your VS Code Copilot workspace. Your VS Code Copilot agent checks this data to ensure the code references the latest Pics.io design iteration. You can also run `list_comments` and `add_comment` in VS Code Copilot to read or post feedback on Pics.io assets. This keeps your engineering team aligned with creative directors without leaving VS Code Copilot.

Setup guide

Set up Pics.io MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Pics.io MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Pics.io tools listed. Try asking: "List my recent Pics.io transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "picsio-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Pics.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Pics.io now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Pics.io MCP in VS Code Copilot

It connects via the MCP Server configured in your VS Code Copilot user or workspace settings. The agent runs Pics.io tools like `list_assets` directly in your VS Code Copilot chat panel.

Yes. Save the server configuration in your project's .vscode/mcp.json file, and every developer on the team gets the Pics.io MCP tools automatically inside VS Code Copilot.

You can ask the VS Code Copilot chat agent to run `search_assets`. It returns the matching Pics.io files, tags, and IDs right in your VS Code Copilot sidebar.

You need VS Code version 1.96 or higher with the GitHub Copilot extension installed to use these custom Pics.io MCP tools.

No. The server runs inside a local V8 sandbox on your machine, ensuring your Pics.io comments, filenames, and metadata remain private in VS Code Copilot.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript