2,500+ MCP servers ready to use
Vinkius

Salesforce Admin & Metadata MCP Server for AutoGen 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Salesforce Admin & Metadata as an MCP tool provider through the Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="salesforce_admin_metadata_agent",
            tools=tools,
            system_message=(
                "You help users with Salesforce Admin & Metadata. "
                "8 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Salesforce Admin & Metadata tools. Connect 8 tools through the Vinkius and assign role-based access — a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

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

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 8 tools from Salesforce Admin & Metadata automatically

Why Use AutoGen with the Salesforce Admin & Metadata MCP Server

AutoGen provides unique advantages when paired with Salesforce Admin & Metadata through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Salesforce Admin & Metadata tools to solve complex tasks

02

Role-based architecture lets you assign Salesforce Admin & Metadata tool access to specific agents — a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive Salesforce Admin & Metadata tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes Salesforce Admin & Metadata tool responses in an isolated environment

Salesforce Admin & Metadata + AutoGen Use Cases

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

01

Collaborative analysis: one agent queries Salesforce Admin & Metadata while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from Salesforce Admin & Metadata, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using Salesforce Admin & Metadata data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process Salesforce Admin & Metadata responses in a sandboxed execution environment

Salesforce Admin & Metadata MCP Tools for AutoGen (8)

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

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

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

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Salesforce Admin & Metadata + AutoGen FAQ

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

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Salesforce Admin & Metadata tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect Salesforce Admin & Metadata to AutoGen

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