2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 8 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Salesforce Admin & Metadata through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "salesforce-admin-metadata": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Salesforce Admin & Metadata Agent",
    instructions:
      "You help users interact with Salesforce Admin & Metadata " +
      "using 8 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Salesforce Admin & Metadata?"
  );
  console.log(result.text);
}

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.

Mastra's agent abstraction provides a clean separation between LLM logic and Salesforce Admin & Metadata tool infrastructure. Connect 8 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

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

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 8 tools from Salesforce Admin & Metadata via MCP

Why Use Mastra AI with the Salesforce Admin & Metadata MCP Server

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

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Salesforce Admin & Metadata without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Salesforce Admin & Metadata tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

Salesforce Admin & Metadata + Mastra AI Use Cases

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

01

Automated workflows: build multi-step agents that query Salesforce Admin & Metadata, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Salesforce Admin & Metadata as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Salesforce Admin & Metadata on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Salesforce Admin & Metadata tools alongside other MCP servers

Salesforce Admin & Metadata MCP Tools for Mastra AI (8)

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

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

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Salesforce Admin & Metadata + Mastra AI FAQ

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

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Salesforce Admin & Metadata to Mastra AI

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