2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 8 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Salesforce Admin & Metadata as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Salesforce Admin & Metadata. "
            "You have 8 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Salesforce Admin & Metadata?"
    )
    print(response)

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.

LlamaIndex agents combine Salesforce Admin & Metadata tool responses with indexed documents for comprehensive, grounded answers. Connect 8 tools through the Vinkius and query live data alongside vector stores and SQL databases in a single turn — ideal for hybrid search, data enrichment, and analytical workflows.

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

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

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 8 tools from Salesforce Admin & Metadata

Why Use LlamaIndex with the Salesforce Admin & Metadata MCP Server

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

01

Data-first architecture: LlamaIndex agents combine Salesforce Admin & Metadata tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Salesforce Admin & Metadata tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Salesforce Admin & Metadata, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Salesforce Admin & Metadata tools were called, what data was returned, and how it influenced the final answer

Salesforce Admin & Metadata + LlamaIndex Use Cases

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

01

Hybrid search: combine Salesforce Admin & Metadata real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Salesforce Admin & Metadata to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Salesforce Admin & Metadata for fresh data

04

Analytical workflows: chain Salesforce Admin & Metadata queries with LlamaIndex's data connectors to build multi-source analytical reports

Salesforce Admin & Metadata MCP Tools for LlamaIndex (8)

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

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

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Salesforce Admin & Metadata + LlamaIndex FAQ

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

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Salesforce Admin & Metadata tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Salesforce Admin & Metadata to LlamaIndex

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