4,000+ servers built on vurb.ts
Vinkius

Stirling PDF MCP Server for VS Code CopilotGive VS Code Copilot instant access to 11 tools to Add Watermark, Cert Sign, Get All Requests, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Stirling PDF MCP Server for VS Code Copilot is a standout in the Productivity category — giving your AI agent 11 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "stirling-pdf": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Stirling PDF and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Stirling PDF
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Stirling PDF MCP Server

Connect your Stirling PDF instance to any AI agent and take full control of your document workflows through natural conversation. This server allows you to process PDF files, convert formats, and monitor your self-hosted infrastructure.

GitHub Copilot Agent mode brings Stirling PDF data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Document Manipulation — Add text watermarks with custom opacity and font sizes, or convert images directly into PDF documents.
  • Digital Security — Sign PDF documents using certificates with specific reasons and location metadata.
  • Server Monitoring — Track application status, version info, and detailed request metrics (POST/GET) across all endpoints.
  • Advanced Operations — Use the generic tool runner to access specialized features like merging, splitting, or extracting images from PDFs.
  • Enterprise Metrics — Access Prometheus metrics for deep observability into your document processing pipeline.

The Stirling PDF MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 11 Stirling PDF tools available for VS Code Copilot

When VS Code Copilot connects to Stirling PDF through Vinkius, your AI agent gets direct access to every tool listed below — spanning pdf-tools, watermarking, pdf-conversion, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add watermark on Stirling PDF

Add a watermark to a PDF document

cert

Cert sign on Stirling PDF

Sign a PDF document with a certificate

get

Get all requests on Stirling PDF

Get POST requests count for all endpoints

get

Get all unique requests on Stirling PDF

Get unique users count for all endpoints

get

Get load on Stirling PDF

Get total count of GET requests

get

Get prometheus metrics on Stirling PDF

Get Prometheus metrics (requires Enterprise tier)

get

Get requests on Stirling PDF

Get total count of POST requests

get

Get status on Stirling PDF

Get application status and version information

get

Get unique requests on Stirling PDF

Get count of unique users for POST requests

img

Img to pdf on Stirling PDF

Convert an image to a PDF document

run

Run generic tool on Stirling PDF

Pass additional parameters as a JSON string. Run any Stirling PDF tool by its ID

Connect Stirling PDF to VS Code Copilot via MCP

Follow these steps to wire Stirling PDF into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Stirling PDF

Ask Copilot: "Using Stirling PDF, help me...". 11 tools available

Why Use VS Code Copilot with the Stirling PDF MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Stirling PDF through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Stirling PDF + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Stirling PDF MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Stirling PDF in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Stirling PDF immediately.

01

"Check the current status and version of my Stirling PDF server."

02

"Add a 'CONFIDENTIAL' watermark to this PDF with 0.5 opacity."

03

"Convert this image to a PDF document named 'report.pdf'."

Troubleshooting Stirling PDF MCP Server with VS Code Copilot

Common issues when connecting Stirling PDF to VS Code Copilot through Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Stirling PDF + VS Code Copilot FAQ

Common questions about integrating Stirling PDF MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Explore More MCP Servers

View all →