MCP Salesforce Integration 🚀

Created By
Tyler4gooda year ago
MCP Salesforce is a server that connects AI assistants with Salesforce using secure OAuth authentication. It simplifies the integration process, offering features like dynamic schema discovery and secure token storage for a smooth user experience. 🐙✨
Overview

What is MCP Salesforce Integration?

MCP Salesforce Integration is a server that connects AI assistants with Salesforce using secure OAuth authentication, simplifying the integration process for developers.

How to use MCP Salesforce Integration?

To use the MCP Salesforce Integration, clone the repository, install dependencies, configure your Salesforce credentials, and start the server to interact with it using RESTful API calls.

Key features of MCP Salesforce Integration?

  • OAuth Authentication: Securely authenticate users and applications.
  • Universal CRUD Operations: Create, Read, Update, and Delete operations on any Salesforce object.
  • Cross-Platform Support: Compatible with Linux and macOS environments.
  • Easy Setup: Simple installation process for quick deployment.
  • Well-Documented: Comprehensive documentation for developers.

Use cases of MCP Salesforce Integration?

  1. Integrating Salesforce data with AI applications.
  2. Automating data management tasks in Salesforce.
  3. Enhancing user authentication processes in applications.

FAQ from MCP Salesforce Integration?

  • What platforms does MCP Salesforce Integration support?

It supports Linux and macOS environments.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • How can I contribute to the project?

You can fork the repository, create a new branch, make changes, and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Tyler4good
Star
0
Language
JavaScript
License
BSD-2-Clause 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)

a day ago
Crevio

2 days ago