2,500+ MCP servers ready to use
Vinkius

Salesforce Admin & Metadata MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 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 Salesforce Admin & Metadata 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": {
    "salesforce-admin-metadata": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Salesforce Admin & Metadata
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 Salesforce Admin & Metadata MCP Server

The Salesforce Admin toolkit for AI agents.

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

What you can do

  • Users — List and search active users with profiles and roles
  • Objects — List all objects, describe schemas with field details
  • Limits — Monitor API calls, storage, and rate limits
  • Metadata — Search Apex classes, triggers, flows via Tooling API
  • Apex — Execute anonymous Apex code
  • Profiles — List security profiles

The Salesforce Admin & Metadata MCP Server exposes 8 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 Salesforce Admin & Metadata to VS Code Copilot via MCP

Follow these steps to integrate the Salesforce Admin & Metadata 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 Salesforce Admin & Metadata

Ask Copilot: "Using Salesforce Admin & Metadata, help me..."8 tools available

Why Use VS Code Copilot with the Salesforce Admin & Metadata MCP Server

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

Salesforce Admin & Metadata + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Salesforce Admin & Metadata 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

Salesforce Admin & Metadata MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect Salesforce Admin & Metadata to VS Code Copilot via MCP:

01

sf_describe_object

Returns every field with: API name, label, data type (string/number/date/reference/picklist/boolean), whether required or nullable, max length, reference target objects (for lookups), and picklist values (for picklist fields). Essential for understanding the data model before creating or querying records. Use when the user asks "what fields does Account have?" or needs to know valid picklist values. Describe the full schema of a Salesforce object — all fields, data types, relationships, picklist values, and validation rules

02

sf_execute_apex

Returns compilation success/failure, execution result, and debug logs. Use for admin tasks (data cleanup, batch operations), testing hypotheses, or running one-off scripts. CAUTION: this executes real code on the org — can modify data. Example: System.debug('Hello World'); Execute anonymous Apex code on the Salesforce org for admin tasks, data fixes, testing, or one-off operations

03

sf_list_objects

Returns all objects with their API name, label, whether they are queryable, createable, and custom. Includes standard objects (Account, Contact, Lead, Opportunity, Case), custom objects (ending in __c), and managed package objects. Essential for data model discovery: "what objects are available?", "do we have a custom invoices object?" List all queryable and createable objects in the Salesforce org — standard, custom, and managed package objects

04

sf_list_profiles

Returns profile name, description, user type, and license type. Profiles control what users can see and do in Salesforce — they define object permissions, field-level security, and page layouts. Use when the user asks about permissions, needs to audit access levels, or wants to understand the security model. List Salesforce profiles (permission sets) with name, description, and user type for access control auditing

05

sf_list_users

Returns user name, email, profile name, role name, user type (Standard/Chatter/etc.), and last login date. Use when the user asks about team members, needs user IDs for record assignment, wants to audit active accounts, or check last login dates for license management. List active Salesforce users with their profile, role, email, user type, and last login date for team management

06

sf_org_limits

Returns current usage vs. maximum for: daily API calls, data storage, file storage, SOQL queries, DML operations, email invocations, and more. Flags any limits below 10% remaining. Use for capacity monitoring, API governance, or when the user asks about org health and limit consumption. Get API and storage usage limits for the Salesforce org — current consumption vs. maximum for API calls, storage, and more

07

sf_search_metadata

Supported objects: ApexClass, ApexTrigger, CustomField, ValidationRule, Flow, FlowDefinition, CustomObject, etc. Example: SELECT Id, Name, Body FROM ApexClass WHERE Name LIKE '%Account%'. Use when the user asks about code, automations, custom fields, or configuration metadata in the org. Search Salesforce metadata via the Tooling API — find Apex classes, triggers, custom fields, validation rules, flows, and more

08

sf_search_users

Returns user name, email, username, profile, role, and login info. Use to find a specific person in the org, look up who owns a record, or get user IDs for API operations. Search Salesforce users by name, email, or username to find specific team members or administrators

Example Prompts for Salesforce Admin & Metadata in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Salesforce Admin & Metadata immediately.

01

"Describe the Opportunity object schema"

02

"Check our API limits"

03

"List all Apex classes containing Account"

Troubleshooting Salesforce Admin & Metadata MCP Server with VS Code Copilot

Common issues when connecting Salesforce Admin & Metadata 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.

Salesforce Admin & Metadata + VS Code Copilot FAQ

Common questions about integrating Salesforce Admin & Metadata 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 Salesforce Admin & Metadata to VS Code Copilot

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