Salesforce HTTP MCP Server

Created By
mrpaapia year ago
salesforce-http-mcp-server
Overview

what is Salesforce HTTP MCP Server?

Salesforce HTTP MCP Server is a Model Context Protocol (MCP) server designed for integrating Salesforce with LangChain, allowing for efficient data queries and tool execution.

how to use Salesforce HTTP MCP Server?

To use the server, clone the repository, install dependencies, configure environment variables with your Salesforce credentials, and start the server. You can then interact with the server using curl commands to get tool manifests and execute queries.

key features of Salesforce HTTP MCP Server?

  • Exposes available tools via /mcp and /sse
  • Executes SOQL queries through a dedicated endpoint
  • API key protection for secure access
  • Rate limiting to prevent abuse of the service

use cases of Salesforce HTTP MCP Server?

  1. Integrating Salesforce data queries into applications using LangChain.
  2. Automating data retrieval from Salesforce for reporting and analytics.
  3. Building custom tools that leverage Salesforce data through the MCP server.

FAQ from Salesforce HTTP MCP Server?

  • What is the purpose of the MCP server?

The MCP server facilitates integration between Salesforce and LangChain, enabling efficient data access and manipulation.

  • How do I secure my API access?

The server uses API key protection to ensure that only authorized users can access its features.

  • Can I execute any SOQL query?

Yes, you can execute any valid SOQL query through the provided endpoint.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mrpaapi
Star
0
Language
JavaScript
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)

20 hours ago
Gpt Scrambler

2 days ago