Sfdcall

Created By
shreymittal1000a year ago
Overview

What is Sfdcall?

Sfdcall is a Salesforce Model Context Protocol (MCP) server that allows users to interact with their Salesforce data and metadata using natural language.

How to use Sfdcall?

Users can choose between a cloud version or a local version. For the cloud version, visit salesforce-mcp.com, authenticate with your Salesforce org, and start chatting with your data. For the local version, configure the environment variables and use it with a compatible AI assistant.

Key features of Sfdcall?

  • Natural language queries for Salesforce data
  • Search functionality across Salesforce records
  • Data structure exploration
  • Record management (create, update, delete)
  • Development tools access
  • Custom application interaction
  • Advanced API features

Use cases of Sfdcall?

  1. Business users can get insights about their Salesforce records.
  2. Developers can manage their Salesforce development environment.
  3. Administrators can configure the platform and automate tasks.

FAQ from Sfdcall?

  • Can I use Sfdcall for all Salesforce objects?

Yes! Sfdcall supports interaction with all Salesforce objects and fields.

  • Is there a cost to use Sfdcall?

The cloud version is free to use, while the local version may require setup.

  • How secure is my data with Sfdcall?

Your Salesforce credentials are stored securely and are not shared with third parties.

Server Config

{
  "mcpServers": {
    "salesforce": {
      "command": "uvx",
      "args": [
        "--from",
        "salesforce-mcp",
        "salesforce"
      ],
      "env": {
        "USERNAME": "YOUR_SALESFORCE_USERNAME",
        "PASSWORD": "YOUR_SALESFORCE_PASSWORD",
        "SECURITY_TOKEN": "YOUR_SALESFORCE_SECURITY_TOKEN"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shreymittal1000
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

3 hours ago