Dockerized Salesforce MCP Server

Created By
Yusful33a year ago
Dockerized Salesforce MCP Server for REST API integration
Overview

what is Dockerized Salesforce MCP Server?

Dockerized Salesforce MCP Server is a project that provides Docker configurations for running the Salesforce MCP Server in a containerized environment, facilitating REST API integration.

how to use Dockerized Salesforce MCP Server?

To use this project, clone the repository from GitHub, build the Docker image, and run the container to set up the Salesforce MCP Server for API integration.

key features of Dockerized Salesforce MCP Server?

  • Easy setup of Salesforce MCP Server using Docker
  • Containerized environment for better resource management
  • Simplified REST API integration with Salesforce services

use cases of Dockerized Salesforce MCP Server?

  1. Integrating Salesforce services into applications using REST APIs.
  2. Testing and developing applications that require Salesforce data.
  3. Running multiple instances of Salesforce MCP Server for different environments.

FAQ from Dockerized Salesforce MCP Server?

  • Is Docker required to run this project?

Yes, Docker is required to build and run the Salesforce MCP Server container.

  • Can I customize the Docker configuration?

Yes, you can modify the Dockerfile and configuration files to suit your needs.

  • Where can I find the documentation?

Documentation can be found in the GitHub repository's README file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Yusful33
Star
0
Language
Shell
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago