3,400+ MCP servers ready to use
Vinkius

Basecamp MCP Server for VS Code CopilotGive VS Code Copilot instant access to 17 tools to Complete Todo, Create Comment, Create Project, and more

Built by Vinkius GDPR 17 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.

Ask AI about this App Connector for VS Code Copilot

The Basecamp app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 17 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Basecamp and 3,400+ 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": {
    "basecamp-alternative": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Basecamp
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 Basecamp MCP Server

Connect your Basecamp account to any AI agent and take full control of your project management, team collaboration, and task tracking through natural conversation.

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

What you can do

  • Project Management — Create, list, update, and inspect projects with full dock metadata (message boards, to-do sets, schedules).
  • To-Do CRUD — Create, update, complete, and uncomplete to-do items across any to-do list, with assignees and due dates.
  • Team Visibility — List all people in your account or within a specific project to find assignee IDs and check roles.
  • Message Boards — Read messages posted on project boards to stay aligned with team decisions and announcements.
  • Comments — Add comments to any recording (to-do, message, document) to provide feedback or status updates.
  • Profile Verification — Retrieve your authenticated profile to confirm connectivity and check access permissions.

The Basecamp MCP Server exposes 17 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.

All 17 Basecamp tools available for VS Code Copilot

When VS Code Copilot connects to Basecamp through Vinkius, your AI agent gets direct access to every tool listed below — spanning task-tracking, team-communication, file-sharing, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

complete_todo

This is separate from archiving or trashing — a completed to-do remains active but is marked as done. Use uncomplete_todo to reverse this action. Mark a to-do item as completed

create_comment

). The recording_id is the unique numeric ID of the item you want to comment on. The content must be provided as rich text (HTML). All subscribers to the recording will be notified of the new comment. Add a comment to any Basecamp recording

create_project

The project will be initialized with default tools (message board, to-do set, schedule, etc.) enabled via its dock. Returns the newly created project with its numeric ID and dock tool IDs. Create a new project in Basecamp

create_todo

Requires the todolist_id and the content (title) of the to-do. Optionally include a rich text description, assignee IDs (array of person IDs), and a due date in YYYY-MM-DD format. The to-do will be created as pending (not completed). Create a new to-do item in a to-do list

get_message

Get full details of a specific message

get_my_profile

Use this to verify connectivity or identify the current operator. Get the authenticated Basecamp user profile

get_person

Use this to look up details about a team member or assignee. Get full details of a specific person

get_project

). The dock contains the IDs you need to access tools like the to-do set or message board. Get full details of a specific project

get_todo

Get full details of a specific to-do item

list_messages

Each message includes title, content preview, author, category, and creation date. You need the message_board_id which can be found via the project dock. List all messages on a project message board

list_people

Useful for finding assignee IDs before creating or updating to-dos. List all people in the Basecamp account

list_project_people

Returns names, emails, and roles. Useful for checking team composition before assigning tasks. List all people assigned to a specific project

list_projects

Optionally filter by status: "active" (default), "archived", or "trashed". Each project includes its name, description, purpose, dock (enabled tools), and bookmark status. List all projects in Basecamp

list_todos

By default returns only pending (not completed) items. Set completed to true to see completed items instead. Each to-do includes its content, assignees, due date, completion status, and comments count. You need the todolist_id which can be found via the project dock. List all to-dos in a specific to-do list

uncomplete_todo

Use this when a previously completed task needs to be reopened or reworked. Mark a completed to-do item as pending again

update_project

At least one of name or description must be provided. Returns the updated project details including the full dock listing. Update an existing project in Basecamp

update_todo

At least one field must be provided. Does not affect completion status — use the complete_todo or uncomplete_todo tools for that. Update an existing to-do item in Basecamp

Connect Basecamp to VS Code Copilot via MCP

Follow these steps to wire Basecamp into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the 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 Basecamp

Ask Copilot: "Using Basecamp, help me...". 17 tools available

Why Use VS Code Copilot with the Basecamp MCP Server

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

Basecamp + VS Code Copilot Use Cases

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

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

01

"List all my active projects in Basecamp."

02

"Create a new to-do 'Review design mockups' in list 592001 and assign it to person 10293 with a due date of 2026-05-15."

03

"Show me the latest messages on the message board of project 48291034."

Troubleshooting Basecamp MCP Server with VS Code Copilot

Common issues when connecting Basecamp 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.

Basecamp + VS Code Copilot FAQ

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