2,500+ MCP servers ready to use
Vinkius

Salesforce Admin & Metadata MCP Server for Claude Desktop 8 tools β€” connect in under 2 minutes

Built by Vinkius GDPR 8 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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.

Claude Desktop is the definitive way to connect Salesforce Admin & Metadata to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the Salesforce Admin & Metadata MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings β†’ Developer β†’ Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Salesforce Admin & Metadata

Look for the πŸ”Œ icon in the chat. your 8 tools are now available

Why Use Claude Desktop with the Salesforce Admin & Metadata MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Salesforce Admin & Metadata through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Salesforce Admin & Metadata + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Salesforce Admin & Metadata MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Salesforce Admin & Metadata MCP Tools for Claude Desktop (8)

These 8 tools become available when you connect Salesforce Admin & Metadata to Claude Desktop 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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

Common issues when connecting Salesforce Admin & Metadata to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the πŸ”Œ icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Salesforce Admin & Metadata + Claude Desktop FAQ

Common questions about integrating Salesforce Admin & Metadata MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the πŸ”Œ icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect Salesforce Admin & Metadata to Claude Desktop

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