2,500+ MCP servers ready to use
Vinkius

Planable MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

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.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Planable and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "planable": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Planable
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 Planable MCP Server

Connect your Planable workspaces directly to your AI agent to radically streamline your social media collaboration loops. You can review scheduled posts, approve mockups, respond to team comments, and oversee the content pipeline directly from your primary interface.

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

What you can do

  • Workspace & Pages — View active workspaces, team members, and all connected social accounts isolated in their respective boundaries.
  • Content Pipeline — Retrieve post drafts, schedule future publications, and query statuses (draft, pending_approval, scheduled, published).
  • Approval Workflow — Radically speed up content sign-off. Instruct your AI to transition posts from pending directly to approved, or formally reject them with custom revision notes.
  • Collaboration — Add, fetch, and monitor chronological threaded comments on any isolated post.

The Planable MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Planable to VS Code Copilot via MCP

Follow these steps to integrate the Planable MCP Server with VS Code Copilot.

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 Planable

Ask Copilot: "Using Planable, help me...". 10 tools available

Why Use VS Code Copilot with the Planable MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Planable 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

Planable + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Planable 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

Planable MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Planable to VS Code Copilot via MCP:

01

add_comment

Add a comment to a Planable post for team collaboration

02

approve_post

Approve a Planable post in the approval workflow. Moves it to scheduled status

03

create_post

Create a Planable post. Instructions: Pass workspace_id, page_id, content text, and scheduled_at (ISO 8601). Post enters approval workflow

04

get_post

Get a Planable post by ID. Returns full content, media, schedule, approval history, and comments

05

list_comments

List comments on a Planable post. Returns comment IDs, authors, and text

06

list_pages

List social pages (connected accounts) in a Planable workspace. Returns page IDs, platform types, and display names

07

list_posts

List posts in a Planable workspace by status. Returns post IDs, content previews, scheduled times, and approval status. Instructions: status = draft|pending_approval|approved|scheduled|published

08

list_workspace_members

List members of a Planable workspace. Returns member IDs, names, emails, and roles

09

list_workspaces

List Planable workspaces. Returns workspace IDs, names, and member counts. Planable is a social collaboration platform for content planning and approval

10

reject_post

Reject a Planable post with feedback. Returns it to draft for revisions

Example Prompts for Planable in VS Code Copilot

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

01

"List all posts in the 'Acme Marketing' workspace that are currently awaiting approval."

02

"Draft a new Twitter post in our workspace announcing our new AI feature."

03

"Reject post `98341x` and tell the team to rewrite the hook, it's too salesy."

Troubleshooting Planable MCP Server with VS Code Copilot

Common issues when connecting Planable to VS Code Copilot through the 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.

Planable + VS Code Copilot FAQ

Common questions about integrating Planable 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.

Connect Planable to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.